Bug 44501 - on 3.4 and 3.5, waking from suspend no longer works. - Asus M2N-SLI
Summary: on 3.4 and 3.5, waking from suspend no longer works. - Asus M2N-SLI
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-11 22:48 UTC by illumilore
Modified: 2013-04-17 06:58 UTC (History)
3 users (show)

See Also:
Kernel Version:
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description illumilore 2012-07-11 22:48:26 UTC 
On Asus M2N-SLI deluxe, on 3.4 and 3.5 mainline (xubuntu 12.04), when the machine is waking from suspend, it goes right back into suspend mode after about 5 seconds. After it goes back into sleep mode, hitting the power button no longer wakes it.
Comment 1 Len Brown 2012-07-17 02:08:41 UTC 
is this still true with 3.5-rc6?
Comment 2 illumilore 2012-07-17 08:38:31 UTC 
yes
Comment 3 Len Brown 2012-07-24 03:18:33 UTC 
If the power button no longer works to wake the machine,
can you wake it by another means?

If yes, please send the complete dmesg output.
If no, how do you know it is is suspended and not powered off?
Comment 4 illumilore 2012-07-24 05:46:04 UTC 
It is in suspend mode, as the power light is flashing.

I can not wake it by other means. I have to toggle the PSU switch in back before the power switch will wake it.
Comment 5 Aaron Lu 2013-03-12 06:16:52 UTC 
Do you still have this problem? Does v3.3 work ok?
Comment 6 Zhang Rui 2013-04-13 16:21:20 UTC 
ping...
Comment 7 Zhang Rui 2013-04-17 06:58:22 UTC 
Bug closed since there is no response from users for more than a month.
illumilore,
please feel free to re-open it if the bug can be reproduced in the latest upstream kernel.
And in that case, please try:
1. build kernel with CONFIG_PM_DEBUG set
2. echo core > /sys/power/pm_test
3. echo mem > /sys/power/pm_test
4. wait for about ten seconds
does the problem still exists in this case?
Note You need to log in before you can comment on or make changes to this bug.