sata drive error after resume from sleep

[RubbelDieCatc]

Binary package hint: acpi-support

I have a AMD2 computer with a M3N78 Mainboard.
Running Kernel 2.6.17 on UBUNTU 8.10

The IDE Interface is a GeForce 8200 running in SATA mode.
Attached is a 1GIG sata disk

After resuming from S3 sleep the system isn't able to access the drive.
I get I/O errors an have to restart. According to the noise the board re-enables the drives correctly.

I tried to disable DMA in /etc/default/acpi-support and I switched into AHCI mode via BIOS-Settings.
btw: S3 sleep and resume on windows works

WORKAROUND: Add pci=nomsi to the kernel boot parameters.

Lsmod:
--------------
00:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1)

HWinfo --disk
--------------
32: IDE 00.0: 10600 Disk
  [Created at block.234]
  UDI: /org/freedesktop/Hal/devices/storage_serial_1ATA_WDC_WD10EACS_65D6B0_WD_WCAU41771461
  Unique ID: 3OOL.GRWJc_NePi6
  Parent ID: WL76.yE7770eiVn1
  SysFS ID: /class/block/sda
  SysFS BusID: 0:0:0:0
  SysFS Device Link: /devices/pci0000:00/0000:00:09.0/host0/target0:0:0/0:0:0:0
  Hardware Class: disk
  Model: "WDC WD10EACS-65D"
  Vendor: "WDC"
  Device: "WD10EACS-65D"
  Revision: "01.0"
  Serial ID: "WD-WCAU41771461"
  Driver: "ahci", "sd"
  Driver Modules: "ahci"
  Device File: /dev/sda
  Device Files: /dev/sda, /dev/disk/by-id/scsi-1ATA_WDC_WD10EACS-65D6B0_WD-WCAU41771461, /dev/disk/by-id/ata-WDC_WD10EACS-65D6B0_WD-WCAU41771461, /dev/disk/by-path/pci-0000:00:09.0-scsi-0:0:0:0, /dev/block/8:0
  Device Number: block 8:0-8:15
  BIOS id: 0x81
  Geometry (Logical): CHS 121601/255/63
  Size: 1953525168 sectors a 512 bytes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #15 (IDE interface)

[RubbelDieCatc (rubbel)]

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

[RubbelDieCatc (rubbel)]

I solved the problem by adding pci=nomsi to the kernel boot parameters.

Everyone with the same board or chipset should have this problem.
So I wonder why there are not more informations about that issue.

MFG... Rubbel

[penalvch (penalvch)]

RubbelDieCatc, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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'.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]