From: John Lash <jlash@speakeasy.net>
To: "Måns Rullgård" <mru@inprovide.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dma errors with sata_sil and Seagate disk
Date: Thu, 2 Dec 2004 22:19:43 -0600 [thread overview]
Message-ID: <20041202221943.3d19590d@tux> (raw)
In-Reply-To: <yw1xvfbkrxn0.fsf@ford.inprovide.com>
On Fri, 03 Dec 2004 02:14:27 +0100
Måns Rullgård <mru@inprovide.com> wrote:
> Alan Cox <alan@lxorguk.ukuu.org.ak> writes:
>
> > On Iau, 2004-12-02 at 10:01, Måns Rullgård wrote:
> Does this mean it is the drives which are faulty, not the controller?
> These drives are both new, so I suppose known problems might have been
> fixed. FWIW, they are reported by the kernel thusly:
>
> Vendor: ATA Model: ST3160827AS Rev: 3.03
> Type: Direct-Access ANSI SCSI revision: 05
> Vendor: ATA Model: ST3160827AS Rev: 3.00
> Type: Direct-Access ANSI SCSI revision: 05
>
I know that the disk that I'm using has been sitting on a shelf since about last June. It still
seems to be a shipping model though. It's showing itself as model: ST380013AS, rev: 3.18.
It would be nice if the problem gets fixed someday. Be even nicer if there was a firmware update
that could be applied to the older drives.....
--john
next prev parent reply other threads:[~2004-12-03 4:19 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
2004-12-03 1:14 ` Måns Rullgård
2004-12-03 4:07 ` Jeff Garzik
2004-12-03 4:19 ` John Lash [this message]
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=20041202221943.3d19590d@tux \
--to=jlash@speakeasy.net \
--cc=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 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.