From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Måns Rullgård" <mru@inprovide.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dma errors with sata_sil and Seagate disk
Date: Thu, 02 Dec 2004 23:33:53 +0000 [thread overview]
Message-ID: <1102030431.7175.9.camel@localhost.localdomain> (raw)
In-Reply-To: <yw1xpt1tuihe.fsf@ford.inprovide.com>
On Iau, 2004-12-02 at 10:01, Måns Rullgård wrote:
> Is there some problem with Seagate drives in general? I'm using two
> ST3160827AS drives on an SI3114 controller, and haven't seen any
> glitches yet. That model is not in the blacklist, and performance is
> what I'd usually expect. Is it pure luck that has kept me away from
> problems?
I've never been able to get a non NDA list of the affected drives. Got
to love vendors some days
next prev parent reply other threads:[~2004-12-03 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 17:50 dma errors with sata_sil and Seagate disk John Lash
2004-12-01 23:41 ` Alan Cox
2004-12-02 4:28 ` John Lash
2004-12-02 10:01 ` Måns Rullgård
2004-12-02 23:33 ` Alan Cox [this message]
2004-12-03 1:14 ` Måns Rullgård
2004-12-03 4:07 ` Jeff Garzik
2004-12-03 4:19 ` John Lash
2004-12-03 4:05 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-12-25 21:02 raz0
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=1102030431.7175.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@inprovide.com \
/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