Suspend with 2.6.0-test7-mm1
Hi,
I've been playing with the suspend features of 2.6.0-test7-mm1 and I can't get it to work. When I do "echo -n standby > /sys/power/state", the screen flickers briefly and then the system is back to normal. In the logs I see the following message:
Oct 20 10:18:12 hansolo kernel: PM: Preparing system for suspend Oct 20 10:18:12 hansolo kernel: Stopping tasks: ============================================================================| Oct 20 10:18:12 hansolo kernel: Restarting tasks... done
Now, I wonder, what is causing the kernel to exit from the suspend immediately? Is it error in suspend code, drivers that doesn't support suspend or some program that is interrupting the sleep? How do I debug this further?
More hw/software info available on request, please CC me on any replies.
Kind regards,
David Härdeman
[email protected]
Quoted 9 lines · David Härdeman
I've been playing with the suspend features of 2.6.0-test7-mm1 and I can't get it to work. When I do "echo -n standby >
/sys/power/state", the screen flickers briefly and then the system is back to normal. In the logs I see the following message:Now, I wonder, what is causing the kernel to exit from the suspend immediately? Is it error in suspend code, drivers that doesn't support suspend or some program that is interrupting the sleep? How do I debug this further?
I've seen this, too. Try "sleep 1; echo -n standby > /sys/power/state". I theory I thought of, is that the system suspends before you have time to release the enter key, and the key release triggers a wakeup. Does this seem reasonable to those more knowledgeable?
Signature · 2 lines
Måns Rullgård [email protected]
Quoted 11 lines
I've been playing with the suspend features of 2.6.0-test7-mm1 and I can't get it to work. When I do "echo -n standby >
/sys/power/state", the screen flickers briefly and then the system is back to normal. In the logs I see the following message:Oct 20 10:18:12 hansolo kernel: PM: Preparing system for suspend Oct 20 10:18:12 hansolo kernel: Stopping tasks: ============================================================================| Oct 20 10:18:12 hansolo kernel: Restarting tasks... done
Quoted 6 lines
Now, I wonder, what is causing the kernel to exit from the suspend immediately? Is it error in suspend code, drivers that doesn't support suspend or some program that is interrupting the sleep? How do I debug this further?
More hw/software info available on request, please CC me on any replies.
Are you using ACPI? If so, could you please send the output of /proc/acpi/sleep? If not, then standby will not work for you at this time.
Thanks,
Pat
Quoted 5 lines · Patrick Mochel
Quoted 1 line
Now, I wonder, what is causing the kernel to exit from the suspend immediately? Is it error in suspend code, drivers that doesn't support suspend or some program that is interrupting the sleep? How do I debug this further?
Are you using ACPI? If so, could you please send the output of
/proc/acpi/sleep? If not, then standby will not work for you at this time.
(david@hansolo:~)$ cat /proc/acpi/sleep S0 S3 S4 S5
I am using ACPI and it seems to work fine (no error messages on boot, able to read battery status, AC adapter status and shutdown/reboot using it).
I seem to recall that "standby" is S1 in ACPI terms. Does the lack of "S1" in the above list mean that my hardware doesn't support standby or that the kernel doesn't?
Also, just to make sure, for the "mem" suspend function, it doesn't matter if the kernel is compiled with CONFIG_PM_DISK or CONFIG_SOFTWARE_SUSPEND or none of them, right? Only CONFIG_ACPI_SLEEP matters?
Regards,
David Härdeman
[email protected]