Re: /proc/acpi/alarm -- does it work or not?

[Pavel Machek]

Hi!

> >I wanted to write some documentation about /proc/acpi/alarm, but
> >failed to make it work. I was putting machine to suspend-to-ram and
> >enabled everything in /proc/acpi/wakeup, still it would not do
> >anything. I even went to bios (thinkpad x32), set "RTC alarm" to
> >enabled and set time there. Nothing interesting
> >happened. /proc/acpi/alarm could not see most of my changes done in
> >BIOS, it only cleared century or something like that.
> >
> >I checked that RTC readout in BIOS shows same thing as system timer.
> >
> >Here are my attempts: [Commands were typed one-after-another where it
> >makes sense, and I left machine suspended for long enough -- timer
> >should have expired]
> It appears we need enable rtc driver to make alarm work.

I enabled CONFIG_RTC:

pavel@amd:/data/l/linux$ grep CONFIG_RTC .config
CONFIG_RTC=y
# CONFIG_RTC_X1205_I2C is not set
pavel@amd:/data/l/linux$

...but /proc/acpi/alarm still behaves very strangely:

2006-01-00 12:42:00
root@amd:/proc/acpi# echo '2006-01-01 12:34:56' > alarm
root@amd:/proc/acpi# cat alarm
2006-01-01 12:34:56
root@amd:/proc/acpi# echo '2006-09-01 12:34:56' > alarm
root@amd:/proc/acpi# cat alarm
2006-01-01 12:34:56
root@amd:/proc/acpi# echo '2006-01-09 12:34:56' > alarm
root@amd:/proc/acpi# cat alarm
2006-01-09 12:34:56
root@amd:/proc/acpi# echo '2006-02-09 12:34:56' > alarm
root@amd:/proc/acpi# cat alarm
2006-01-09 12:34:56
root@amd:/proc/acpi#

...why does it hate february and september?

							Pavel

-- 
Thanks, Sharp!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/