From: Jeff Garzik <jgarzik@pobox.com>
To: "R. J. Wysocki" <rjwysocki@sisk.pl>, Ricky Beam <jfbeam@bluetronic.net>
Cc: Eric Buddington <ebuddington@verizon.net>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: SATA 3112 errors on 2.6.7
Date: Sat, 19 Jun 2004 16:19:08 -0400 [thread overview]
Message-ID: <40D49FBC.7040900@pobox.com> (raw)
In-Reply-To: <200406192210.05455.rjwysocki@sisk.pl>
R. J. Wysocki wrote:
> On Saturday 19 of June 2004 01:06, Ricky Beam wrote:
>
>>On Sat, 19 Jun 2004, R. J. Wysocki wrote:
>>
>>>Are your drives out of Seagate, maybe? If not, what make are they?
>>
>>(As I said in a previous email...) 4 x Seagate ST3160023AS's RAID0'd
>>together in a BIOS "raid" mode compatable manner.
>
>
> Sorry, I should have noticed.
>
> Anyway, it looks like a pattern is forming which smells bad to me.
>
> Apparently, we have:
> 1) A serious error condition that occurs on Seagate SATA drives connected to
> Silicon Image controllers.
> 2) As of today we can say that it only occurs on Seagate drives (Ricky, do I
> remember correctly that you see faulty behavior of such drives with a 3ware
> RAID?).
> 3) The error is reported by the kernel like that:
I wonder if it helps to add the Seagate drive to the sata_sil blacklist?
/* TODO firmware versions should be added - eric */
struct sil_drivelist {
const char * product;
unsigned int quirk;
} sil_blacklist [] = {
{ "ST320012AS", SIL_QUIRK_MOD15WRITE },
{ "ST330013AS", SIL_QUIRK_MOD15WRITE },
{ "ST340017AS", SIL_QUIRK_MOD15WRITE },
{ "ST360015AS", SIL_QUIRK_MOD15WRITE },
{ "ST380023AS", SIL_QUIRK_MOD15WRITE },
{ "ST3120023AS", SIL_QUIRK_MOD15WRITE },
[...]
next prev parent reply other threads:[~2004-06-19 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 21:07 SATA 3112 errors on 2.6.7 Eric Buddington
2004-06-18 0:40 ` Ricky Beam
2004-06-18 6:08 ` Matthias Urlichs
2004-06-18 16:28 ` Ricky Beam
2004-06-18 22:18 ` R. J. Wysocki
2004-06-18 23:06 ` Ricky Beam
2004-06-19 20:10 ` R. J. Wysocki
2004-06-19 20:19 ` Jeff Garzik [this message]
2004-06-19 21:20 ` Ricky Beam
2004-06-20 2:38 ` kernel
2004-06-22 20:17 ` Ricky Beam
2004-06-19 21:35 ` Ricky Beam
2004-06-22 18:34 ` George Georgalis
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=40D49FBC.7040900@pobox.com \
--to=jgarzik@pobox.com \
--cc=ebuddington@verizon.net \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjwysocki@sisk.pl \
/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