Comment 0 for bug 1181878

This bug is actually related to bugs 1057664 and 1171560, and is an upstream bug.

When I suspend my system to RAM, actually suspend does not work and instead I get a blinking cursor, and after some time system turns back again.

After some debugging, I've found this within the logs of dmesg :

[ 3476.964420] Suspending console(s) (use no_console_suspend to debug)
[ 3476.964837] sd 7:0:0:0: [sdd] Synchronizing SCSI cache
[ 3476.964860] sd 6:0:0:0: [sdc] Synchronizing SCSI cache
[ 3476.964952] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 3476.964964] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[ 3476.965068] sd 6:0:0:0: [sdc] Stopping disk
[ 3476.965087] sd 7:0:0:0: [sdd] Stopping disk
[ 3476.965121] sd 3:0:0:0: [sdb] Stopping disk
[ 3476.965141] sd 2:0:0:0: [sda] Stopping disk
[ 3476.982377] i8042 kbd 00:0b: System wakeup enabled by ACPI
[ 3476.982396] i8042 aux 00:0a: System wakeup disabled by ACPI
[ 3476.982486] parport_pc 00:09: disabled
[ 3476.982582] serial 00:08: disabled
[ 3476.982585] serial 00:08: System wakeup disabled by ACPI
[ 3507.790314] ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3507.790320] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3507.790322] ata8.00: failed command: STANDBY IMMEDIATE
[ 3507.790324] ata3.00: failed command: STANDBY IMMEDIATE
[ 3507.790329] ata8.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3507.790329] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3507.790334] ata3.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3507.790334] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3507.790335] ata8.00: status: { DRDY }
[ 3507.790337] ata3.00: status: { DRDY }
[ 3507.790339] ata8: hard resetting link
[ 3507.790340] ata8: nv: skipping hardreset on occupied port
[ 3507.790341] ata3: hard resetting link
[ 3507.790342] ata3: nv: skipping hardreset on occupied port
[ 3508.257491] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3508.257493] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3508.273615] ata8.00: configured for UDMA/133
[ 3508.273618] ata8.00: device reported invalid CHS sector 0
[ 3508.273629] ata8: EH complete
[ 3508.273634] sd 7:0:0:0: [sdd] START_STOP FAILED
[ 3508.273636] sd 7:0:0:0: [sdd]
[ 3508.273637] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3508.273638] sd 7:0:0:0: [sdd]
[ 3508.273640] Sense Key : Aborted Command [current] [descriptor]
[ 3508.273642] sd 7:0:0:0: [sdd]
[ 3508.273643] Add. Sense: No additional sense information
[ 3508.273652] dpm_run_callback(): scsi_bus_suspend+0x0/0x40 returns 134217730
[ 3508.273657] PM: Device 7:0:0:0 failed to suspend async: error 134217730
[ 3508.273696] ata3.00: configured for UDMA/133
[ 3508.273698] ata3.00: device reported invalid CHS sector 0
[ 3508.273704] ata3: EH complete
[ 3508.273714] sd 2:0:0:0: [sda] START_STOP FAILED
[ 3508.273717] sd 2:0:0:0: [sda]
[ 3508.273718] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3508.273720] sd 2:0:0:0: [sda]
[ 3508.273722] Sense Key : Aborted Command [current] [descriptor]
[ 3508.273723] sd 2:0:0:0: [sda]
[ 3508.273724] Add. Sense: No additional sense information
[ 3508.273734] dpm_run_callback(): scsi_bus_suspend+0x0/0x40 returns 134217730
[ 3508.273739] PM: Device 2:0:0:0 failed to suspend async: error 134217730
[ 3508.273787] PM: Some devices failed to suspend

The command sent to trigger these logs was :
echo 'mem' > /sys/power/state
With pm-suspend they do not appear.

On my system, devices sda and sdc actually point to HDDs WD Caviar Black with firmware 05.01D05. sdb and sdd point to other HDD models, not these ones. And it turns out that I get errors with these specific devices, sda and sdc. The bug is not always reproducible, sometimes suspend goes well, but sometimes it doesn't. I suspect there's something wrong with the commands sent to these devices.

The bug started to be reproducible with Ubuntu 12.10, prior to this while I already owned these HDDs. The HDDs themselves are not culprit as the suspend command works on MS Windows 7. And my configuration is also not culprit as I tested with a raring liveCD and the result is the same.

I don't know who must be contacted in the kernel team in order to look at this issue, if you could indicate me who this would help.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-21-generic 3.8.0-21.32
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: julien 3629 F.... pulseaudio
 /dev/snd/controlC0: julien 3629 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
Date: Mon May 20 01:48:34 2013
HibernationDevice: RESUME=UUID=1e2e6306-5da1-44ae-98dd-d137e96a8425
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 002 Device 002: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
 Bus 002 Device 003: ID 046d:0928 Logitech, Inc. QuickCam Express
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic root=UUID=53dfbfeb-5955-48e2-9039-e6c3b9b219d0 ro ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-21-generic N/A
 linux-backports-modules-3.8.0-21-generic N/A
 linux-firmware 1.106
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-04-07 (42 days ago)
WpaSupplicantLog:

dmi.bios.date: 10/02/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701
dmi.board.name: M2N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer