From: Robert Hancock <hancockrwd@gmail.com>
To: Thomas Fjellstrom <tfjellstrom@strangesoft.net>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: via 8237 sata errors
Date: Sun, 30 May 2010 12:40:04 -0600 [thread overview]
Message-ID: <4C02B104.4010900@gmail.com> (raw)
In-Reply-To: <201005292046.06344.tfjellstrom@strangesoft.net>
On 05/29/2010 08:46 PM, Thomas Fjellstrom wrote:
> I'm getting a rather nasty set of messages from dmesg when trying to use
> a couple SATA II WD 2TB Green drives with an older system (via 8237 based).
> They seem to work fine on a newer p35 based system.
..
> [ 283.308963] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [ 283.309007] ata2.00: BMDMA stat 0x4
> [ 283.309045] ata2.00: failed command: READ DMA
> [ 283.309089] ata2.00: cmd c8/00:08:08:08:30/00:00:00:00:00/e0 tag 0 dma 4096 in
> [ 283.309091] res 41/04:00:08:08:30/00:00:00:00:00/e0 Emask 0x1 (device error)
> [ 283.309171] ata2.00: status: { DRDY ERR }
> [ 283.309207] ata2.00: error: { ABRT }
> [ 283.324886] ata2.00: configured for UDMA/133
> [ 283.324904] ata2: EH complete
It's not really clear why the drive is returning command aborted on a
read, there's no other error bits to indicate an uncorrectable error or
a CRC error. Is it only the one drive that's giving the errors?
next prev parent reply other threads:[~2010-05-30 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 2:46 via 8237 sata errors Thomas Fjellstrom
2010-05-30 18:40 ` Robert Hancock [this message]
2010-05-30 18:57 ` Thomas Fjellstrom
2010-05-30 19:33 ` Thomas Fjellstrom
2010-05-30 19:40 ` Robert Hancock
2010-05-30 19:48 ` Thomas Fjellstrom
2010-05-31 1:19 ` Thomas Fjellstrom
2010-06-02 21:10 ` failed command FLUSH CACHE EXT (was: Re: via 8237 sata errors) Thomas Fjellstrom
2010-06-02 23:05 ` Robert Hancock
2010-06-02 23:42 ` Thomas Fjellstrom
2010-06-03 8:23 ` failed command FLUSH CACHE EXT Tejun Heo
2010-06-03 8:41 ` Thomas Fjellstrom
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=4C02B104.4010900@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tfjellstrom@strangesoft.net \
/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).