Created attachment 107691 [details] dmesg output after 2nd (failed) resume First suspend/resume works, second resume always goes straight to the "Chromeos unverified os warning" screen (which is normal for regular boot). Tested with Xubuntu 12.10 and 13.10 alpha 2 live boot disks, and also with a fresh install and latest mainline kernel. Debugging instructions from https://wiki.ubuntu.com/DebuggingKernelSuspend yield: [ 0.774083] Magic number: 0:967:362 [ 0.774087] hash matches /home/apw/COD/linux/drivers/base/power/main.c:643 And /proc/apci/wakeup (doesn't change after first suspend): Device S-state Status Sysfs node LID0 S4 *enabled TPAD S3 *enabled pnp:00:00 TSCR S3 *enabled pnp:00:01 HDEF S4 *disabled pci:0000:00:1b.0 EHC1 S4 *enabled pci:0000:00:1d.0 EHC2 S4 *enabled pci:0000:00:1a.0 Now there are 3 peculiarities: 1) When booting with "no_console_suspend", after the second (failed) resume, it quickly displays the previous console output (with my pm-suspend command) right after the chromeos warning but right before regular booting. 2) The keyboard backlight is not restored with the first resume. 3) After 1st resume, the console displays twice: 1-1.2: string descriptor 0 read error: -22 I don't have external USB devices connected, but the internal ones are: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0489:e057 Foxconn / Hon Hai Bus 001 Device 003: ID 2232:1033 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanks! Willem
Please try this: https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt Simply put, you can try: # cd /sys/power # echo devices > pm_test # echo mem > state multiple times and see if anything wrong occur.
Apparently, Duncan Laurie has figured it had to do with the tpm_tis driver: https://plus.google.com/109560881064626882142/posts It's now working for me.