Comment 9 for bug 362242

Did the machine break while going to sleep or waking up?

During resume from suspend the system goes through an initial wakeup period of approximately 4 seconds when hard disk activity can be seen, the display backlight turns on but the user is not returned to X. Hard disk activity due to running applications (indexing, etc) can be seen after resume, but the user cannot input any commands to the system. The user is unable to switch virtual terminals, restart X or restart/power down the system using the soft-shutdown via powerbutton. The powerbutton must be held to shutdown the system.

Is it reproducible?

When running FGLRX driver in Jaunty and Karmic wake from suspend fails approximately 20%.

Did it work before?

Not with FGLRX, but with RadeonHD suspend has failed to resume once with Karmic alpha (out of ~40 suspend cycles).

Do you end up with flashing caps-lock or similar?

Only during one failure to resume when running Jaunty with FGLRX, most failures simply provide the user with a black screen and an unresponsive system.

cat /proc/cmdline

root=UUID=cf378b06-0657-4fee-b3f0-2807d06bd372 ro quiet nosplash resume=/dev/mapper/swap i8042.reset no_console_suspend

cat /etc/initramfs-tools/conf.d/resume

RESUME=/dev/mapper/swap

Other information

It seems to happen on both battery and charger connected conditions. System uses encrypted /var /home and swap partitions.