Bug 7265 - S3: no wakeup - ThinkPad X31
Summary: S3: no wakeup - ThinkPad X31
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-04 18:58 UTC by Aaron G
Modified: 2007-10-06 14:22 UTC (History)
2 users (show)

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


Attachments

Description Aaron G 2006-10-04 18:58:28 UTC
Most recent kernel where this bug did not occur:
Distribution:
Hardware Environment: IBM Thinkpad X31
Software Environment: Linux-2.6.18-git22
Problem Description: System enters sleep and then does not wake up. In the old
kernel system would sleep, then wake up when the power button was pushed, but it
would shut down immediately afteward because the power down event was not ignored.

Steps to reproduce: 
1) echo "mem" >/sys/power/state
system goes to sleep
2) press power button
system appears to be waking up, but then nothing happens, screen remains blank
3) press power button again
nothing happens.
Comment 1 Adrian Bunk 2006-10-04 20:36:53 UTC
What is "the old kernel"?

IOW, what was the last working kernel?
Comment 2 Len Brown 2006-10-04 21:35:12 UTC
2.6.18 worked fine and 2.6.18-git22 fails to wake on power button press? 
Curious, because there have been no ACPI-related patches between 
these releases.  Any chance you can do a git-bisect? 
 
Comment 3 Aaron G 2006-10-05 08:08:04 UTC
2.6.17-gentoo-r8 "worked", it was broken in 2.6.18-gentoo, and then I upgraded
to the latest kernel to see if the bug was still present (which it is).

I put "worked" in quotation marks because resume never really worked. That is to
say that the computer would come back to life, but the power button push event
wasn't trapped, so it would immediately enter runlevel 0 upon resume.
Comment 4 Len Brown 2007-09-06 15:19:40 UTC
Is this still a problem in linux-2.6.22.stable or later?
Comment 5 Adrian Bunk 2007-10-06 14:22:54 UTC
Please reopen this bug if it's still present with kernel 2.6.22.

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