/proc/acpi/alarm -- does it work or not?
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]
root@amd:/proc/acpi# cat alarm 2005-12-00 01:03:24 root@amd:/proc/acpi# echo '0-0-0 22:35:00' > alarm root@amd:/proc/acpi# cat alarm 0005-12-00 22:35:00 root@amd:/proc/acpi# s2ram Freezing cpus ... Stopping tasks: ====================================| ACPI: PCI interrupt for device 0000:02:01.0 disabled ACPI: PCI interrupt for device 0000:02:00.1 disabled ACPI: PCI interrupt for device 0000:02:00.0 disabled radeonfb (0000:01:00.0): suspending to state: 2... radeonfb (0000:01:00.0): resuming from state: 2...to 64er 10 Dec 2004 Restarting tasks... done Thawing cpus ... root@amd:/proc/acpi# date Sun Dec 25 22:36:46 CET 2005 root@amd:/proc/acpi# cat alarm 0005-12-00 22:35:00 root@amd:/proc/acpi#
root@amd:/proc/acpi# cat alarm 0005-12-00 22:35:00 root@amd:/proc/acpi# echo '*-*-* 22:40:00' > alarm root@amd:/proc/acpi# cat alarm 0005-12-00 22:35:00 root@amd:/proc/acpi# echo '2005-12-25 22:40:00' > alarm root@amd:/proc/acpi# cat alarm 2005-12-25 22:40:00 root@amd:/proc/acpi# date Sun Dec 25 22:37:53 CET 2005 root@amd:/proc/acpi# s2ram Freezing cpus ... Stopping tasks: =====================================| ACPI: PCI interrupt for device 0000:02:01.0 disabled ACPI: PCI interrupt for device 0000:02:00.1 disabled ACPI: PCI interrupt for device 0000:02:00.0 disabled radeonfb (0000:01:00.0): suspending to state: 2... radeonfb (0000:01:00.0): resuming from state: 2...to 64er 10 Dec 2004 Restarting tasks... done Thawing cpus ... root@amd:/proc/acpi# date Sun Dec 25 22:41:14 CET 2005 root@amd:/proc/acpi#
...so... what am I doing wrong? Is thinkpad x32 machine where it does not work?
Pavel
Signature · 8 lines
Thanks, Sharp! ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
A message that is not in the archive (sent off-list or not yet received): 20051226204305.GA2028-I/[email protected]
Thus wrote Pavel Machek:
[...]
Last time I checked (2.6.15-rc[45]) it worked fine -- I use it routinely for S3 stress-testing (speaking of which, my machine has just failed to resume after some 20 days of uptime and > 150 S3 cycles).
Quoted 7 lines
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]
root@amd:/proc/acpi# cat alarm 2005-12-00 01:03:24 root@amd:/proc/acpi# echo '0-0-0 22:35:00' > alarm
You got it mixed up. It's either
"2005-12-28 19:50:00" for absolute or
"+0000-00-00 00:01:00" for relative.
RTC IRQ counter is incremented whenever the timer triggers, regardless of whether the system is up or down (my system, at least).
HTH, best regards,
Signature · 9 lines
Karol 'sziwan' Kozimor sziwan-DETuoxkZsSqrDJvtcaxF/[email protected] ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click