From: Thomas Fjellstrom <tfjellstrom@strangesoft.net>
To: linux-kernel@vger.kernel.org
Cc: Robert Hancock <hancockrwd@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: via 8237 sata errors
Date: Sun, 30 May 2010 13:33:50 -0600 [thread overview]
Message-ID: <201005301333.51149.tfjellstrom@strangesoft.net> (raw)
In-Reply-To: <201005301257.31839.tfjellstrom@strangesoft.net>
On May 30, 2010, Thomas Fjellstrom wrote:
> On May 30, 2010, Robert Hancock wrote:
> > 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?
>
> I'm not entirely sure if its the same drive each time. I can make sure
> today. The fun part is it works fine in a different machine. Where as it
> will start erroring out like that almost right away in the via based
> machine. When its doing that, its also making some fairly scary (for a
> hard drive) noises, but since it doesn't do that in the p35 machine I'm
> really hoping it isn't the drive.
I've started up a dd on each drive, just for kicks, and reading from both of
them at the same time seems to work fine on the via chipset. Given this
little tid-bit, it seems its only once md-raid is setup on the drives does
one of them freak out.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
--
Thomas Fjellstrom
tfjellstrom@strangesoft.net
next prev parent reply other threads:[~2010-05-30 19:33 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
2010-05-30 18:57 ` Thomas Fjellstrom
2010-05-30 19:33 ` Thomas Fjellstrom [this message]
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=201005301333.51149.tfjellstrom@strangesoft.net \
--to=tfjellstrom@strangesoft.net \
--cc=hancockrwd@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.