public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Lash <jlash@speakeasy.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dma errors with sata_sil and Seagate disk
Date: Wed, 1 Dec 2004 22:28:02 -0600	[thread overview]
Message-ID: <20041201222802.4545e663@tux> (raw)
In-Reply-To: <1101944482.30990.74.camel@localhost.localdomain>

On Wed, 01 Dec 2004 23:41:22 +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Mer, 2004-12-01 at 17:50, John Lash wrote:
> > I don't see any indication that Seagate has released any public firmware
> > upgrades for this drive. Anybody have a suggestion?
> 
> Don't mix seagate drives and SI311x hardware is the best suggestion.
> Even if you activate the workaround for the problem you take a
> performance hit.
> 
> Please send Jeff Garzik a patch for the the change you made of course.
> 
> 

Thanks Alan, that's pretty clear ;-) Yes, performance hit, big time, 9-10 MB/sec, load average
through the roof on a big copy. Pretty much what I was expecting though. I'll look around work and
see if there is anybody I can trade with. Odd that those two devices are so wildly incompatible.

I'll roll up a patch for the change in the morning.

--john

  reply	other threads:[~2004-12-02  4:28 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 [this message]
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
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=20041201222802.4545e663@tux \
    --to=jlash@speakeasy.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox