Bug 23562 - Acer AO521 Does Not Wake
Summary: Acer AO521 Does Not Wake
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: All Linux
: P1 high
Assignee: power-management_other
URL:
Keywords:
: 23572 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-11-22 23:19 UTC by Michael Daum
Modified: 2012-05-24 07:48 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.34
Subsystem:
Regression: No
Bisected commit-id:


Attachments
PM_TRACE dmesg (31.14 KB, text/plain)
2010-11-27 15:58 UTC, mikezackles
Details
DSDT (522.55 KB, text/plain)
2010-11-27 16:01 UTC, mikezackles
Details
lspci of AO521 (1.82 KB, text/plain)
2010-11-30 03:24 UTC, Michael Daum
Details
contents of /proc/interrupts (1.05 KB, text/plain)
2010-12-02 22:15 UTC, mikezackles
Details

Description Michael Daum 2010-11-22 23:19:58 UTC
AO521 goes to sleep on lid close, but refuses to wake (freezes?).

Steps to replicate:

Close lid.
Wait for suspend LED cadence.
Wait a minute to ensure computer is in sleep.
Open lid and push keyboard key or power button to wake.
Computer wakes (e.g. computer lights indicate computer is awake), but is frozen with no visual, black screen (e.g. backlight is functioning on screen).

NOTES:  I currently do not have another computer available to attempt SSH, so it may still be functioning "under the hood", so to speak.

***MAY BE HELPFUL***
Kernel is using patch offered in Bug #19602, which was the only way to enable the kernel to see the battery/processor states...
( https://bugzilla.kernel.org/show_bug.cgi?id=19602 )

There is also quite a bit of dumped information in that report, but I will be happy to assist in any way that is asked.
Comment 1 mikezackles 2010-11-27 15:55:48 UTC
On my AO521, this only works when the acpi kernel parameter is set to noirq using the uswsusp backend.  (I haven't gotten around to trying it with the kernel backend yet, but I'll try to give it a shot in the next couple of days).  Suspend and hibernate both work using Windows 7.
Comment 2 mikezackles 2010-11-27 15:58:44 UTC
Created attachment 38302 [details]
PM_TRACE dmesg

I don't have a PM_TRACE for the most recent kernel, but here's one from 2.6.34 that I have saved from a little while back.  (hash matches drivers/base/power/main.c:437).
Comment 3 mikezackles 2010-11-27 16:01:10 UTC
Created attachment 38312 [details]
DSDT

This is from the most recent BIOS update.
Comment 4 mikezackles 2010-11-29 13:20:55 UTC
I have the same issue when using the kernel backend.  It only works when I use the acpi=noirq kernel parameter.
Comment 5 Zhang Rui 2010-11-30 03:05:37 UTC
*** Bug 23572 has been marked as a duplicate of this bug. ***
Comment 6 Michael Daum 2010-11-30 03:14:06 UTC
Sorry about the duplicate...  Bugzilla was being slow at the time and didn't show me that it had actually submitted it the first time.
Comment 7 Len Brown 2010-11-30 03:17:48 UTC
mikezackles, so everything works fine with upstream suspend to ram
and resume if you boot the system with "acpi=noirq"?
Michael Daum, is that the case for your system too?

There are a number of things to try in
Documentation/power/basic-pm-debugging.txt
in the source tree, can you try them out?

if this is about the backlight not coming back on,
then this is a video driver bug. please identify
the graphics hardware by supplying the output from lspci
Comment 8 Michael Daum 2010-11-30 03:24:03 UTC
No, the backlight does indeed come on, the issue is that nothing else happens on the screen beyond blank pixels.  I have tried both radeon DRI and fglrx with the same results.

lspci is coming...
Comment 9 Michael Daum 2010-11-30 03:24:49 UTC
Created attachment 38602 [details]
lspci of AO521
Comment 10 mikezackles 2010-12-02 05:46:21 UTC
Len, yes everything works using acpi=noirq.  I'm headed to sleep right now, but I'll set up a PM_DEBUG kernel in the morning and run through the tests.
Comment 11 mikezackles 2010-12-02 18:54:59 UTC
Len, I ran all 5 tests 3 times each on an unpatched mainline kernel.  The freezer, devices, platform, and processors tests all succeeded every time, and the core test failed every time.  After passing the acpi=noirq kernel param, the core test succeeds.
Comment 12 Rafael J. Wysocki 2010-12-02 20:30:22 UTC
Please attach the contents of /proc/interrupts .
Comment 13 mikezackles 2010-12-02 22:15:55 UTC
Created attachment 38902 [details]
contents of /proc/interrupts
Comment 14 Zhang Rui 2012-01-18 02:25:28 UTC
It's great that kernel bugzilla is back.

can you please verify if the problem still exists in the latest upstream
kernel?
Comment 15 Zhang Rui 2012-05-24 07:48:03 UTC
bug closed as there is no response from the bug reporter.
please feel free to reopen it if the problem still exists in the latest upstream kernel.

Note You need to log in before you can comment on or make changes to this bug.