From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
My ThinkPad X24 laptop claims to support ACPI sleep mode S3:
% cat /proc/acpi/sleep
S0 S3 S4 S5
However, attempting to go into S3 mode hangs the laptop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. echo 3 >/proc/acpi/sleep
Actual Results: A console message appears reporting that all
processes are being stopped. This is quickly followed by a second
message: "PM: Entering state."
Fan and hard drive now turn off. The screen goes blank, but not dark.
The LCD is still being illuminated; it clearly is not powered off.
Crescent-shaped indicator light on laptop base lights up.
Laptop is now completely unresponsive. Tapping the "Fn" key does not
bring it back. Closing and opening the lid does not bring it back.
Tapping the power key does not bring it back. Even holding down the
power key for several seconds, which should turn the laptop off, has
no effect. The only way to recover from this state is to remove all
power sources (battery & AC).
Expected Results: The LCD should have powered off. The laptop should
have woken up from S3 in response to tapping the "Fn" key, opening the
lid, or any of the other usual triggers.
The bug is consistently reproducible even when booted into single user
mode. This eliminates X11, network drivers, and most modules as
possible culprits. When my laptop is running in single user mode, the
only loaded modules are:
For what it's worth, this bug still appears exactly as describe above
using the current Fedora Core 2 kernel-2.6.7-1.494.2.2.
Can you try the latest FC2 kernel, which is similar to the latest FC3
kernel (or FC3 in itself) and see if it fixes your issues
Colin, thanks for suggesting I take a second look at this. Using
kernel-2.6.9-1.3_FC2, my laptop no longer hangs when put into S3 sleep
mode. It sleeps when asked and comes back when asked. Hooray!
There are a few outstanding problems. The internal LCD display
remains illuminated, and the kernel prints debug messages regarding
calling a "sleeping function" from an "invalid context".
However, the hang is gone, so this bug is now resolved. I will file
two new reports for the outstanding problems noted above.