My home server was suspending a waking quite nicely - recently it has broken I am pretty sure on or around the 23rd of sept. I am guessing this was probably during an update. Anyway it will suspend and wake once and then when trying to suspend it fails

It is using this kernel:

3.2.0-31-generic-pae

I have tried an echi script similr to this:
http://ubuntuforums.org/showpost.php...0&postcount=19

this does not work.

here is a bit of the syslog



Code:
Oct 10 20:13:10 localhost kernel: [ 4003.357124] dvb-usb: Hauppauge Nova-T Stick successfully deinitialized and disconnected.
Oct 10 20:13:11 localhost kernel: [ 4003.625346] PM: Syncing filesystems ... done.
Oct 10 20:13:11 localhost kernel: [ 4003.633717] PM: Preparing system for mem sleep
Oct 10 20:13:13 localhost kernel: [ 4003.688079] Freezing user space processes ... (elapsed 0.01 seconds) done.
Oct 10 20:13:13 localhost kernel: [ 4003.704218] Freezing remaining freezable tasks ... (elapsed 0.03 seconds) done.
Oct 10 20:13:13 localhost kernel: [ 4003.736201] PM: Entering mem sleep
Oct 10 20:13:13 localhost kernel: [ 4003.736290] Suspending console(s) (use no_console_suspend to debug)
Oct 10 20:13:13 localhost kernel: [ 4003.737033] sd 3:0:0:0: [sde] Synchronizing SCSI cache
Oct 10 20:13:13 localhost kernel: [ 4003.737315] sd 3:0:0:0: [sde] Stopping disk
Oct 10 20:13:13 localhost kernel: [ 4003.737453] sd 2:0:0:0: [sdd] Synchronizing SCSI cache
Oct 10 20:13:13 localhost kernel: [ 4003.737563] sd 2:0:0:0: [sdd]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 10 20:13:13 localhost kernel: [ 4003.737586] pm_op(): scsi_bus_suspend+0x0/0x20 returns -5
Oct 10 20:13:13 localhost kernel: [ 4003.737600] PM: Device 2:0:0:0 failed to suspend async: error -5
Oct 10 20:13:13 localhost kernel: [ 4003.737645] serial 00:09: disabled
Oct 10 20:13:13 localhost kernel: [ 4003.737755] serial 00:09: wake-up capability disabled by ACPI
Oct 10 20:13:13 localhost kernel: [ 4004.273331] PM: suspend of drv:sd dev:3:0:0:0 complete after 536.300 msecs
Oct 10 20:13:13 localhost kernel: [ 4004.273400] PM: Some devices failed to suspend
Oct 10 20:13:13 localhost kernel: [ 4004.273601] sd 3:0:0:0: [sde] Starting disk
Oct 10 20:13:13 localhost kernel: [ 4004.274681] serial 00:09: activated
Oct 10 20:13:13 localhost kernel: [ 4006.236223] PM: resume of drv:sd dev:3:0:0:0 complete after 1962.619 msecs
Oct 10 20:13:13 localhost kernel: [ 4006.236314] PM: resume of drv:scsi_device dev:3:0:0:0 complete after 1962.678 msecs
Oct 10 20:13:13 localhost kernel: [ 4006.236323] PM: resume of drv:scsi_disk dev:3:0:0:0 complete after 1960.348 msecs
Oct 10 20:13:13 localhost kernel: [ 4006.236443] PM: resume of devices complete after 1963.034 msecs
Oct 10 20:13:13 localhost kernel: [ 4006.236669] PM: resume devices took 1.964 seconds
Oct 10 20:13:13 localhost kernel: [ 4006.236714] PM: Finishing wakeup.
Oct 10 20:13:13 localhost kernel: [ 4006.236718] Restarting tasks ... done.
I have disabled the script that put the machine into suspend as the syslog was filling up with errors caused by the suspend not working e.g.

Code:
Oct 11 09:09:32 localhost kernel: [41178.816123] af9015: bulk message failed:-19 (9/0)
Oct 11 09:09:32 localhost kernel: [41178.816183] af9015: bulk message failed:-19 (9/0)
Oct 11 09:09:32 localhost kernel: [41178.816207] af9015: bulk message failed:-19 (9/0)
Oct 11 09:09:32 localhost kernel: [41178.816228] af9015: bulk message failed:-19 (9/0)
Oct 11 09:09:32 localhost kernel: [41178.816253] af9015: bulk message failed:-19 (9/0)
Oct 11 09:09:33 localhost kernel: [41179.828054] DiB0070 I2C read failed
Oct 11 09:09:33 localhost kernel: [41179.828064] DiB0070 I2C write failed
Oct 11 09:09:40 localhost kernel: [41187.324076] DiB0070 I2C read failed
Oct 11 09:09:40 localhost kernel: [41187.324090] DiB0070 I2C write failed
Oct 11 09:09:44 localhost kernel: [41190.776093] sd 7:0:0:0: [sde] Unhandled error code
Oct 11 09:09:44 localhost kernel: [41190.776102] sd 7:0:0:0: [sde]  Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Oct 11 09:09:44 localhost kernel: [41190.776111] sd 7:0:0:0: [sde] CDB: Write(10): 2a 00 a1 14 00 47 00 00 10 00
Oct 11 09:09:44 localhost kernel: [41190.776133] end_request: I/O error, dev sde, sector 2702442567
Oct 11 09:09:44 localhost kernel: [41190.776144] quiet_error: 96 callbacks suppressed
Oct 11 09:09:44 localhost kernel: [41190.776150] Buffer I/O error on device sde1, logical block 337805313
Oct 11 09:09:44 localhost kernel: [41190.776156] lost page write due to I/O error on sde1
Oct 11 09:09:44 localhost kernel: [41190.776170] Buffer I/O error on device sde1, logical block 337805314
Oct 11 09:09:44 localhost kernel: [41190.776176] lost page write due to I/O error on sde1
Oct 11 09:09:44 localhost kernel: [41190.816087] sd 7:0:0:0: [sde] Unhandled error code
Oct 11 09:09:44 localhost kernel: [41190.816097] sd 7:0:0:0: [sde]  Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Oct 11 09:09:44 localhost kernel: [41190.816107] sd 7:0:0:0: [sde] CDB: Write(10): 2a 00 a1 14 03 d7 00 00 08 00
Oct 11 09:09:44 localhost kernel: [41190.816128] end_request: I/O error, dev sde, sector 2702443479
Oct 11 09:09:44 localhost kernel: [41190.816140] Buffer I/O error on device sde1, logical block 337805427
Oct 11 09:09:44 localhost kernel: [41190.816146] lost page write due to I/O error on sde1
these error do not normally occur - the dib0070 one caused the the suspend/wake issue almost certainly.


I have googled my fingers to the bone - so I thought would ask here!