{DRDY ERR} trouble with CD-ROM

[Bogdan Butnaru]

Hello! I’ve noticed my kernel keeps complaining with messages like this one:

***************************************************************
[ 2077.071793] ata3.00: exception Emask 0x40 SAct 0x0 SErr 0x80800 action 0x6
[ 2077.110113] ata3.00: irq_stat 0x40000001
[ 2077.148025] ata3: SError: { HostInt 10B8B }
[ 2077.185771] sr 2:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[ 2077.185795] ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 2077.185797] res 51/24:03:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
[ 2077.262254] ata3.00: status: { DRDY ERR }
[ 2077.300418] ata3: hard resetting link
[ 2077.647888] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2077.654835] ata3.00: configured for UDMA/100
[ 2077.677866] ata3: EH complete
***************************************************************

These are spammed to the text console (how I noticed them), and now that I look the logs are filled with them. Grepping for “ata3: hard resetting link” in /var/log shows 1112 occurrences in kern.log, 883 in syslog and another 1303 in kern.log.1

As far as I can tell “ata3” means my DVD drive. (I couldn’t find out at first how to translate libata’s identifiers to something I can identify, and I had a brief moment of panic thinking the hard drive was dying...) Syslog says:

May 10 18:33:59 arkyn kernel: [ 2.305607] ata3: SATA max UDMA/133 abar m2048@0xfb205000 port 0xfb205200 irq 45
May 10 18:33:59 arkyn kernel: [ 2.654011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 10 18:33:59 arkyn kernel: [ 2.657084] ata3.00: ATAPI: HL-DT-ST DVDRAM GH22NS50, TN02, max UDMA/100
May 10 18:33:59 arkyn kernel: [ 2.660951] ata3.00: configured for UDMA/100

When I first noticed it there was a block of messages like above every few seconds. I rebooted and it still happened for a while afterwards, but it stopped now. I opened and closed the DVD door a couple of times, but I can’t tell if that’s what made it stop or it just hit an error limit.

A bit of Googling found the link below, which seems to show a very similar problem from 2006; I’ve no idea how to determine if it’s actually related (my computer is just a couple months old):
http://forum.soft32.com/linux/PATCH-ahci-fix-ati-sb600-sata-IRQ_TF_ERR-ftopict341444.html

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-9-generic 2.6.38-9.43
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bogdanb 1470 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfb200000 irq 47'
   Mixer name : 'Realtek ALC892'
   Components : 'HDA:10ec0892,10438436,00100302'
   Controls : 32
   Simple ctrls : 18
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfb080000 irq 17'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100200'
   Controls : 16
   Simple ctrls : 4
Date: Tue May 10 19:06:14 2011
HibernationDevice: RESUME=/dev/sda4
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-9-generic root=UUID=5df87911-7544-4c36-bcbe-ba10d44c2112 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-9-generic N/A
 linux-backports-modules-2.6.38-9-generic N/A
 linux-firmware 1.52
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-05-02 (8 days ago)
dmi.bios.date: 11/25/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0805
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[penalvch (penalvch)]

Bogdan Butnaru, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please 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 <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

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', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Launchpad Janitor (janitor)]

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