Hmm.... I wonder why nobody else has such a problem. The behaviour is reproducible with any other debian based distribution. The driver is unable to re-enable the sata-interface.
Anyway... here is a part of the resume error message: [ 112.105053] ata7.00: configured for UDMA/33 [ 112.368240] ata7.01: configured for UDMA/33 [ 112.505914] sd 0:0:0:0: [sda] Starting disk [ 117.260254] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 117.988150] ata1: link is slow to respond, please be patient (ready=0) [ 120.228074] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 122.260235] ata3.00: qc timeout (cmd 0xec) [ 122.260239] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 122.260240] ata3.00: revalidation failed (errno=-5) [ 122.744223] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 125.228087] ata1.00: qc timeout (cmd 0xec) [ 125.228090] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 125.228091] ata1.00: revalidation failed (errno=-5) [ 125.712195] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 132.744018] ata3.00: qc timeout (cmd 0xec) [ 132.744021] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 132.744023] ata3.00: revalidation failed (errno=-5) [ 133.228054] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 135.712106] ata1.00: qc timeout (cmd 0xec) [ 135.712109] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 135.712110] ata1.00: revalidation failed (errno=-5) [ 136.196188] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 163.228060] ata3.00: qc timeout (cmd 0xec) [ 163.228063] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 163.228065] ata3.00: revalidation failed (errno=-5) [ 163.228066] ata3.00: disabled [ 163.228072] ata3: hard resetting link [ 163.712147] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 163.712150] ata3: EH complete [ 166.196204] ata1.00: qc timeout (cmd 0xec) [ 166.196207] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 166.196208] ata1.00: revalidation failed (errno=-5) [ 166.196210] ata1.00: disabled [ 166.196213] ata1: hard resetting link [ 166.736163] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 166.736166] ata1: EH complete [ 166.736180] sd 0:0:0:0: [sda] START_STOP FAILED [ 166.736181] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK [ 166.736264] PM: Device 0:0:0:0 failed to resume: error 262144 [ 166.736658] sd 2:0:0:0: [sdb] Starting disk [ 166.736667] sd 2:0:0:0: [sdb] START_STOP FAILED [ 166.736668] sd 2:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK [ 166.736749] PM: Device 2:0:0:0 failed to resume: error 262144 [ 167.081205] PM: resume devices took 55.908 seconds -- sata drive error after resume from sleep https://bugs.launchpad.net/bugs/354462 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
