public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: linux-kernel@vger.kernel.org
Subject: Serial ATA Lockups
Date: Wed, 28 Dec 2005 07:25:20 +0000	[thread overview]
Message-ID: <43B23DE0.5080201@dbservice.com> (raw)

My setup: Shuttle XPC Barebone, AMD CPU, two serial ATA disks in a 
software raid setup.
When the system is under heavy load (start World of Warcraft, dd 
if=/dev/zero of=/part/file etc) I get these messages in dmesg:

ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }

over and over, pages with these messages.
The system will eventually lockup hard, HDD led is on, no disk activity, 
I have to reboot the system. Some kernels ago (2.6.14.2) I got a kernel 
backtrace on the console, I don't remember exactly anymore but there was 
something with scsi_resume(). I don't get this backtrace with this 
kernel: 2.6.15-rc6-gd5ea4e26, now it just locks up hard.

Sometimes I can't even boot (like just before), it locked up before init 
could be started. And I've seen this on my console (transcript):

command 0x35 timeout, stat 0xd0 host_stat 0x21
translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
status=0xd0 { busy }
SCSI error: return code = 0x8000002
sda: Current: sense key = 0xB
end_request: I/O error, dev sda, sector [sector #]
ATA abnormal status 0xD0 on port 0x9f7

Its very hard recover from a hard lockup because at the next reboot, the 
kernel wants to RESYNC the raid arrays and this causes heavy load which 
again causes a hard lockup. And endless loop. Sometimes, I can boot and 
then I change to 'init 2' to stop as many services as I can and unmount 
as many partitions as I can but even then it sometimes locks up again.

The Barebone SATA chip supports SATA-II, but the harddrives are SATA-I. 
The two disks are Seagate 120GB. I've had problems with the harddrives 
before, I've had them on a ICP Vortex SATA hardware-raid controller and 
sometimes, one disk would fail and I'd have to rebuild the array. It was 
always the same disk, and I don't think it one that I have in my new 
computer now.

Can this be fixed in the kernel? Or do I have to buy new harddisks?

tom

             reply	other threads:[~2005-12-28  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28  7:25 Tomas Carnecky [this message]
     [not found] <5oCZ7-3FB-17@gated-at.bofh.it>
2005-12-28  7:33 ` Serial ATA Lockups Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43B23DE0.5080201@dbservice.com \
    --to=tom@dbservice.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox