From: Philip Langdale <philipl@mail.utexas.edu>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: CRC errors with sata drives connected to ULi M5281
Date: Thu, 23 Feb 2006 08:25:58 -0800 [thread overview]
Message-ID: <43FDE216.9000802@mail.utexas.edu> (raw)
Hi all,
I happen to have a motherboard with an onboard M5281
controller that provides extra sata and pata ports.
Up until now, I've never had a use for it, but I've
been trying to use it with some spare drives I now
have, and it's been resulting in errors while reading
from the drive, and the system locks up with a sufficiently
long sustained transfer.
I observe identical behaviour with 2.6.15.4 and 2.6.16-rc4,
which doesn't really surprise me as the uli driver is basically
unchanged between them.
My symptoms appear identical to the ones described here:
http://www.ussg.iu.edu/hypermail/linux/kernel/0503.2/1378.html
> ata13: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
> ata13: status=0x51 { DriveReady SeekComplete Error }
> ata13: error=0x84 { DriveStatusError BadCRC }
In my case, I have a uniprocessor preempt kernel.
I have tried with maxtor and hitachi drives which both work
fine when connected to a via vt6421 controller card that I
also have.
Interestingly, the frequency of BadCRC errors seems to be
inversely related to the transfer speed. I tried forcing
it to use PIO for transfers and this caused a significant
increase in the number of errors reported. In fact, it
seemed to me that more errors were reported with the hitatchi
vs. the maxtor and those report themselves as udma/100 and
udma/133 respectively.
I'm rather out of ideas for what to do next, and I'd really
like to be able to take advantage of this controller if I can.
Thanks,
--phil
reply other threads:[~2006-02-23 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43FDE216.9000802@mail.utexas.edu \
--to=philipl@mail.utexas.edu \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).