[M2N-SLI DELUXE] Plugging in Western Digital Caviar Black 500 GB / 1 TB prevents suspend

[Julien Aubin]

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 :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+attachment/3744189/+files/dmesg

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.

WORKAROUND: - Run as root :
echo 0 > /sys/power/pm_async

(added to /etc/rc.local to be permanent)

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

[Julien Aubin (gojulgarbmail)]

After re-reading the bug report I found out that the HDD brand there is not the culprit, as /dev/sdd points to a WD Caviar Blue. Anyway there's something fishy with the HDD driver there.

[Julien Aubin (gojulgarbmail)]

Actually this looks like a NVidia MCP5x bug, as explained there :
http://marc.info/?l=linux-ide&m=136297331308023&w=2

[Julien Aubin (gojulgarbmail)]

Seems to be related to this bug :
https://bugzilla.kernel.org/show_bug.cgi?id=48951

[Brad Figg (brad-figg)]

This change was made by a bot.

[Julien Aubin (gojulgarbmail)]

I've remarked that the change to udev rules proposed as a workaround does not work, since attribute power/async is not even present under the /sys tree.

My output for udevinfo for one of my HDDs :
administrateur@pcathlon64:~$ sudo udevadm info -a -p /sys/block/sda
[sudo] password for administrateur:

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:05.0/ata1/host0/target0:0:0/0:0:0:0/block/sda':
    KERNEL=="sda"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{ro}=="0"
    ATTR{size}=="1953525168"
    ATTR{stat}==" 43323 186686 3049670 698632 4428 7667 293952 81904 0 144364 780504"
    ATTR{range}=="16"
    ATTR{discard_alignment}=="0"
    ATTR{events}==""
    ATTR{ext_range}=="256"
    ATTR{events_poll_msecs}=="-1"
    ATTR{alignment_offset}=="0"
    ATTR{inflight}==" 0 0"
    ATTR{removable}=="0"
    ATTR{capability}=="50"
    ATTR{events_async}==""

  looking at parent device '/devices/pci0000:00/0000:00:05.0/ata1/host0/target0:0:0/0:0:0:0':
    KERNELS=="0:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{rev}=="05.0"
    ATTRS{type}=="0"
    ATTRS{scsi_level}=="6"
    ATTRS{model}=="WDC WD1002FAEX-0"
    ATTRS{state}=="running"
    ATTRS{queue_type}=="simple"
    ATTRS{iodone_cnt}=="0xbfa2"
    ATTRS{iorequest_cnt}=="0xc6b7"
    ATTRS{queue_ramp_up_period}=="120000"
    ATTRS{timeout}=="30"
    ATTRS{evt_media_change}=="0"
    ATTRS{ioerr_cnt}=="0x12"
    ATTRS{queue_depth}=="31"
    ATTRS{vendor}=="ATA "
    ATTRS{device_blocked}=="0"
    ATTRS{iocounterbits}=="32"

  looking at parent device '/devices/pci0000:00/0000:00:05.0/ata1/host0/target0:0:0':
    KERNELS=="target0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS==""

  looking at parent device '/devices/pci0000:00/0000:00:05.0/ata1/host0':
    KERNELS=="host0"
    SUBSYSTEMS=="scsi"
    DRIVERS==""

  looking at parent device '/devices/pci0000:00/0000:00:05.0/ata1':
    KERNELS=="ata1"
    SUBSYSTEMS==""
    DRIVERS==""

  looking at parent device '/devices/pci0000:00/0000:00:05.0':
    KERNELS=="0000:00:05.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="sata_nv"
    ATTRS{irq}=="21"
    ATTRS{subsystem_vendor}=="0x1043"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x010185"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000f"
    ATTRS{device}=="0x037f"
    ATTRS{enable}=="1"
    ATTRS{msi_bus}==""
    ATTRS{local_cpulist}=="0-3"
    ATTRS{vendor}=="0x10de"
    ATTRS{subsystem_device}=="0x8239"
    ATTRS{numa_node}=="0"
    ATTRS{d3cold_allowed}=="1"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc2-saucy/

[Julien Aubin (gojulgarbmail)]

Hi,

The kernel bug actually exists upstream, which is not surprising as the bug I referenced is marked as "won't fix". However it turns out that there's one 1-line offending commit which broke everything, as stated in comment #10 of the bug. The commit is :
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=966f1212e1ac5fe3ddf04479d21488ddb36a2608

I can try a patched 3.8.0-xx kernel packaged for Ubuntu Raring with this fix, in order to test.

Rgds,

Julien.

[Julien Aubin (gojulgarbmail)]

Hi,

Here's a workaround for the bug, from kernel.org bug mentioned above :

- Run as root :
echo 0 > /sys/power/pm_async

(added to /etc/rc.local to be permanent)

[penalvch (penalvch)]

Cut from Bug Description.

[penalvch (penalvch)]

Julien Aubin, could you please test the latest upstream kernel available (v3.11-rc1-saucy) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Julien Aubin (gojulgarbmail)]

Hi,

Tested with kernel 3.11 after upgrading to saucy, and unfortunately this does not fix the bug. :-(

[penalvch (penalvch)]

Julien Aubin, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc2-saucy/ and comment to the results?

[Julien Aubin (gojulgarbmail)]

Hi, bug is still there with upstream... :-(

[penalvch (penalvch)]

Julien Aubin, did this problem not occur in a release prior to Quantal?

[Julien Aubin (gojulgarbmail)]

Hi,

The bug never occured before Quantal. It has been a regression introduced with kernel 3.4 or 3.5 if I recall well (version mentioned in the bug report on kernel.org)

Rgds,

[penalvch (penalvch)]

Julien Aubin, the next step is to bisect between Precise and Quantal, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Julien Aubin (gojulgarbmail)]

Hi,

I've unfortunately no way to get back that early, but the offending commit is listed in the bug report I've mentioned on kernel.org, see :

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=966f1212e1ac5fe3ddf04479d21488ddb36a2608

Rgds,