Comment 2 for bug 1065840

Revision history for this message
Fabio Marconi (fabiomarconi) wrote : Re: xubuntu 12.10 suspend wakes right back up

Oct 12 00:42:29 htpc kernel: [ 53.856263] ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 12 00:42:29 htpc kernel: [ 53.856265] ata8.00: failed command: STANDBY IMMEDIATE
Oct 12 00:42:29 htpc kernel: [ 53.856270] ata8.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 12 00:42:29 htpc kernel: [ 53.856270] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Oct 12 00:42:29 htpc kernel: [ 53.856271] ata8.00: status: { DRDY }
Oct 12 00:42:29 htpc kernel: [ 53.856276] ata8: hard resetting link
Oct 12 00:42:29 htpc kernel: [ 53.856277] ata8: nv: skipping hardreset on occupied port
Oct 12 00:42:29 htpc kernel: [ 54.324031] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 12 00:42:29 htpc kernel: [ 54.340196] ata8.00: configured for UDMA/100
Oct 12 00:42:29 htpc kernel: [ 54.340199] ata8.00: device reported invalid CHS sector 0
Oct 12 00:42:29 htpc kernel: [ 54.340210] ata8: EH complete
Oct 12 00:42:29 htpc kernel: [ 54.340223] sd 7:0:0:0: >[sda] START_STOP FAILED
Oct 12 00:42:29 htpc kernel: [ 54.340225] sd 7:0:0:0: >[sda]
Oct 12 00:42:29 htpc kernel: [ 54.340226] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 12 00:42:29 htpc kernel: [ 54.340227] sd 7:0:0:0: >[sda]
Oct 12 00:42:29 htpc kernel: [ 54.340228] Sense Key : Aborted Command [current] [descriptor]
Oct 12 00:42:29 htpc kernel: [ 54.340231] sd 7:0:0:0: >[sda]
Oct 12 00:42:29 htpc kernel: [ 54.340232] Add. Sense: No additional sense information
Oct 12 00:42:29 htpc kernel: [ 54.340246] dpm_run_callback(): scsi_bus_suspend+0x0/0x20 returns 134217730
Oct 12 00:42:29 htpc kernel: [ 54.340249] PM: suspend of drv:sd dev:7:0:0:0 complete after 30555.449 msecs
Oct 12 00:42:29 htpc kernel: [ 54.340254] PM: Device 7:0:0:0 failed to suspend async: error 134217730
Oct 12 00:42:29 htpc kernel: [ 54.340290] PM: Some devices failed to suspend

Seems that the hard disk is in a bad state, can you analize it with a diagnostic tool ?
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad