Ubuntu

Repeated DRDY ERR / ICRC ABRT msgs on 2.6.31-19-server

Reported by IsaacByers on 2010-03-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

I have a system running Ubuntu Karmic 64-bit server edition:

- Shuttle SG31G2 with Intel Core2Quad Q6600 processor

- 4GB DDR2 800 (PC2 6400) SDRAM
- 1 Samsung Spinpoint 750GB hard drive
- 1 Seagate Barracuda ST31500341AS 1.5TB drive

And it's been running fine for over a year now, until just a couple days ago when the following started repeatedly showing up both on the console and on dmesg output:

[35876.766809] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[35876.767629] ata3.00: BMDMA stat 0x66
[35876.768440] ata3.00: cmd 35/00:00:47:8c:ea/00:04:49:00:00/e0 tag 0 dma 524288 out
[35876.768442] res 51/84:9c:ab:8e:ea/84:01:49:00:00/e0 Emask 0x30 (host bus error)
[35876.770223] ata3.00: status: { DRDY ERR }
[35876.771132] ata3.00: error: { ICRC ABRT }
[35876.772099] ata3: soft resetting link
[35877.060320] ata3.00: configured for UDMA/133
[35877.127629] ata3.01: configured for UDMA/133
[35877.127652] ata3: EH complete

Replaced hard drives thinking they were faulty, only to find that with known good hard drives installed, the messages continued.

Ultimately, I noted the messages started with the installation of latest 2.6.31-19-server kernel. Used GRUB2 to boot intointo previous kernel release: 2.6.31-17-server. Sure enough, the messages stopped.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D1c', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer', '/dev/sequencer2'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfdff8000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,12970000,00100001'
   Controls : 35
   Simple ctrls : 18
Date: Tue Mar 2 07:19:50 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=7c3bc62a-f6ea-4cc9-b189-354a01273fa8
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Shuttle Inc SG31
Package: linux-server 2.6.31.19.32
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-server root=UUID=88f0c52a-6c22-496f-8e7b-80197b92e8ff ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-server
RelatedPackageVersions:
 linux-backports-modules-2.6.31-19-server N/A
 linux-firmware 1.26
RfKill:

SourcePackage: linux-meta
Uname: Linux 2.6.31-19-server x86_64
WifiSyslog:

dmi.bios.date: 08/23/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FG31
dmi.board.vendor: Shuttle Inc
dmi.board.version: V10
dmi.chassis.type: 3
dmi.chassis.vendor: Shuttle Inc
dmi.chassis.version: G2
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/23/2007:svnShuttleInc:pnSG31:pvrV10:rvnShuttleInc:rnFG31:rvrV10:cvnShuttleInc:ct3:cvrG2:
dmi.product.name: SG31
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc

IsaacByers (scrdpoet) wrote :
Andy Whitcroft (apw) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and tag it kj-linux-meta, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
IsaacByers (scrdpoet) wrote :

FYI: updated the box in question to the 2.6.31-20-server kernel that was released today, and the error continue. Have gone back 2.6.31-16.

Unfortunately, I'm new and inexperienced to the bug submission process here. What is the best way to carry this bug forward to 2.6.31-20? Or, should it just be left as-is?

tags: added: karmic
jetole (jetole) wrote :

I can confirm this has occurred to me in the last week on ubuntu 8.10 and 9.10 both on Ubuntu desktop AMD64. I noticed the error when my system started freezing and during a reboot when fsck failed due to a failing hard drive but I saw this error come up intermittently while scanning the hard drive. The hard drive was in fact dying and so I replaced it that day with a new Western Digital Caviar Black and installed Ubuntu 9.10. Within a few hours I started seeing this output in dmesg for the new drive.

jetole (jetole) wrote :

I don't retract my comment but at the same time I think this may actually be a limited hardware failure on my machine. I am not certain yet but this seems like it may be limited to one specific SATA port which has been used for a long time but may no longer work. I will update this post when I know for sure.

jetole (jetole) wrote :

I retract my comment. I had a physical port on my sata bus which was dying. I moved the drive to another port and I no longer receive these error notifications.

Brad Figg (brad-figg) on 2010-07-22
tags: added: kj-triage
Brad Figg (brad-figg) on 2011-05-04
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: b73a1py79

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers