5

This question covers one reason a computer might immediately wake after suspend: How do I prevent immediate wake up from suspend and/or hibernation?

I seem to have a different one. After a recent security patch update on Ubuntu 11.04 - the Natty Narwhal, the machine wakes up immediately after suspending. The relevant log lines seem to be:

Oct  5 09:01:02 hardhat kernel: [585671.422973] PM: Syncing filesystems ... done.
Oct  5 09:01:02 hardhat kernel: [585671.475283] PM: Preparing system for mem sleep
Oct  5 09:01:02 hardhat kernel: [585671.475399] Freezing user space processes ... (elapsed 0.01 seconds) done.
Oct  5 09:01:02 hardhat kernel: [585671.490593] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Oct  5 09:01:02 hardhat kernel: [585671.510542] PM: Entering mem sleep
Oct  5 09:01:02 hardhat kernel: [585671.510558] Suspending console(s) (use no_console_suspend to debug)
Oct  5 09:01:02 hardhat kernel: [585671.511061] sd 1:0:1:0: [sdc] Synchronizing SCSI cache
Oct  5 09:01:02 hardhat kernel: [585671.511124] sd 0:0:1:0: [sdb] Synchronizing SCSI cache
Oct  5 09:01:02 hardhat kernel: [585671.511193] sd 0:0:1:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct  5 09:01:02 hardhat kernel: [585671.511200] pm_op(): scsi_bus_suspend+0x0/0x20 returns -5
Oct  5 09:01:02 hardhat kernel: [585671.511203] PM: Device 0:0:1:0 failed to suspend async: error -5
Oct  5 09:01:02 hardhat kernel: [585671.511296] sd 1:0:1:0: [sdc] Stopping disk
Oct  5 09:01:02 hardhat kernel: [585672.039397] PM: suspend of drv:sd dev:1:0:1:0 complete after 529.213 msecs
Oct  5 09:01:02 hardhat kernel: [585672.039486] PM: Some devices failed to suspend
Oct  5 09:01:02 hardhat kernel: [585672.039507] sd 0:0:0:0: [sda] Starting disk
Oct  5 09:01:02 hardhat kernel: [585672.039696] sd 0:0:1:0: [sdb] Starting disk
Oct  5 09:01:02 hardhat kernel: [585672.039776] sd 1:0:1:0: [sdc] Starting disk
Oct  5 09:01:02 hardhat kernel: [585672.039839] sd 0:0:1:0: [sdb] START_STOP FAILED
Oct  5 09:01:02 hardhat kernel: [585672.039843] sd 0:0:1:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct  5 09:01:02 hardhat kernel: [585672.039853] pm_op(): scsi_bus_resume_common+0x0/0x60 returns 262144
Oct  5 09:01:02 hardhat kernel: [585672.039861] PM: Device 0:0:1:0 failed to resume async: error 262144
Oct  5 09:01:02 hardhat kernel: [585673.533456] PM: resume of drv:sd dev:1:0:1:0 complete after 1496.158 msecs
Oct  5 09:01:02 hardhat kernel: [585673.533550] PM: resume of drv:scsi_device dev:1:0:1:0 complete after 1496.242 msecs
Oct  5 09:01:02 hardhat kernel: [585673.533557] PM: resume of drv:scsi_disk dev:1:0:1:0 complete after 1496.157 msecs
Oct  5 09:01:02 hardhat kernel: [585673.533645] PM: resume of devices complete after 1496.634 msecs
Oct  5 09:01:02 hardhat kernel: [585673.533782] PM: resume devices took 1.500 seconds
Oct  5 09:01:02 hardhat kernel: [585673.533801] PM: Finishing wakeup.
Improve this question
3
  • Can you please state what log file you're looking at (incl the path)? That way, others who are learning to navigate Linux can follow along. Thanks! :)
    – Nathan J.B.
    Apr 17, 2014 at 7:13
  • That's a system log (syslog)
    – Bryce
    Apr 23, 2014 at 19:35
  • So, /var/log/syslog -- right? Thanks!
    – Nathan J.B.
    Apr 23, 2014 at 20:36

1 Answer 1

Reset to default
1

Well, sd 0:0:1:0 is most likely a USB drive which doesn't play nicely with suspend. Just remove it when you're not using it.

Improve this answer
1
  • There are no USB drives (there is a USB card reader).
    – Bryce
    Aug 12, 2014 at 20:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.