I’m running 11.3 swapless on a HP dv6z (AMD Turion dual-core processor, 3GB RAM, ATI Radeon HD 3200 graphics), customized by replacing the original hard drive with an Intel 40 GB X25-V SSD.
About 2 out of 3 times the suspend to RAM and resume work fine, taking a couple of seconds to suspend and resuming almost instantaneously. The other times, suspend seems to hang for about 30 seconds or so with the monitor displaying a console login (same as I see briefly when a suspend works). The display eventually shuts off, and the light is blinking on/off as in a normal suspend, but when I resume I’m unable to login. The message I get when I try to login is “Cannot unlock the session because the authentication system failed to work, you must kill kscreenlocker (pid 12,139) manually”; if I go to a console screen and try to login as root to do the kill I get “end-request: I/O error, dev sda sector …” repeated many times, and cannot login that way, either.
pm-suspend.log shows the hang-up occurring at the same point each time, after all the sleep.d operations. Here’s a sample:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend:success.
/usr/lib/pm-utils/sleep.d/02rtcwake suspend suspend:rtcwake alarm not enabled in /etc/pm/config.d/rtcwake.config, doing nothing…
not applicable.
/usr/lib/pm-utils/sleep.d/06autofs suspend suspend:Shutting down automount …done
success.
/usr/lib/pm-utils/sleep.d/30s2disk-check suspend suspend:success.
/usr/lib/pm-utils/sleep.d/45pcmcia suspend suspend:ejecting PCMCIA cards…
success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/50rcnetwork suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend:success.
/usr/lib/pm-utils/sleep.d/80acpi-fan suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/80videobios suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/95packagekit suspend suspend:success.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:success.
/usr/lib/pm-utils/sleep.d/99Zgrub suspend suspend:success.
/usr/lib/pm-utils/sleep.d/99info suspend suspend:not applicable.
/usr/lib/pm-utils/sleep.d/99video suspend suspend:disabled.
Fri Jul 23 09:39:54 NZST 2010: performing suspend
INFO: using built-in quirks database from HAL.
INFO: S2RAM_OPTS from HAL quirks: ’ '.
If I try to resume after this nothing more is added to the log. On a resume from a successful suspend, the log continues on:
switching from vt7 to vt1… succeeded
fbcon fb0 state 1
fbcon fb0 state 0
switching back to vt7… succeeded
Thu Jul 22 12:55:12 NZST 2010: Awake.
Thu Jul 22 12:55:12 NZST 2010: Running hooks for resume
…
Any ideas?