public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clem Taylor <clemtaylor@comcast.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Any news on a higher performance sata_sil SIL_QUIRK_MOD15WRITE workaround?
Date: Fri, 13 Aug 2004 00:18:56 -0400	[thread overview]
Message-ID: <411C4130.4000303@comcast.net> (raw)
In-Reply-To: <411B118B.4040802@pobox.com>

Jeff Garzik wrote:
> Get a different controller + disk combination.

I don't want to dump the disks, but I may be ordering a 3ware controller 
in the near future. The only reason I didn't get a 3ware controller in 
the first place was that the Sil 3114 was on the motherboard.

> The problem is that the Silicon Image controller sends unusual -- but 
> legal -- block sizes to the SATA device.
> 
> Older Seagates cannot cope with this unique, but spec-correct behavior.

I thought that the Seagate ST3160023AS was a fairly new drive. I noticed 
a comment that version 3.18 of the firmware may not suffer from this 
problem, can anyone confirm this? I'm going to try removing my drive 
from the blacklist and see what happens.

>> It would seem that the root of the problem is a Seagate issue. Does 
>> anyone know if Seagate fixed the problem with a firmware update? 
> 
> You could find out for us, and let us know :)

I tried, my contact at Seagate doesn't seem to be with them anymore (I 
haven't worked in the storage space in quite some time).

                 Thanks for the help,
                 Clem

  parent reply	other threads:[~2004-08-13  4:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12  5:16 Any news on a higher performance sata_sil SIL_QUIRK_MOD15WRITE workaround? Clem Taylor
2004-08-12  6:43 ` Jeff Garzik
2004-08-12 12:00   ` Alan Cox
2004-08-12 15:16     ` Jeff Garzik
2004-08-12 19:59       ` Alan Cox
2004-08-12 21:03         ` Jeff Garzik
2004-08-12 20:37           ` Alan Cox
2004-08-13  4:18   ` Clem Taylor [this message]
2004-08-13 12:13     ` Alan Cox
2004-08-16 18:49       ` Eric Mudama

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=411C4130.4000303@comcast.net \
    --to=clemtaylor@comcast.net \
    --cc=jgarzik@pobox.com \
    --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