From: Jens Axboe <jens.axboe@oracle.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jeff@garzik.org>, Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Tejun Heo <htejun@gmail.com>
Subject: Re: [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver
Date: Thu, 22 Feb 2007 16:41:56 +0100 [thread overview]
Message-ID: <20070222154156.GB4740@kernel.dk> (raw)
In-Reply-To: <45DDAB95.6070903@rtr.ca>
On Thu, Feb 22 2007, Mark Lord wrote:
> Jens Axboe wrote:
> >>Robert Hancock wrote:
> >..
> >>>+ /* The following blacklist entries are taken from the Windows
> >>>+ driver .inf files for the Silicon Image 3124 and 3132. */
> >>>+ { "Maxtor 7B250S0", "BANC1B70", ATA_HORKAGE_NONCQ, },
> >>>+ { "HTS541060G9SA00", "MB3OC60D", ATA_HORKAGE_NONCQ, },
> >>>+ { "HTS541080G9SA00", "MB4OC60D", ATA_HORKAGE_NONCQ, },
> >>>+ { "HTS541010G9SA00", "MBZOC60D", ATA_HORKAGE_NONCQ, },
> >>Do we have information that these drives fail on non-SiI controllers?
> >>
> >>Sometimes the problem can be related to a single family of controllers.
> >
> >I don't know about the Hitachi's, but the Maxtor with that firmware is
> >definitely broken. It _appeared_ to work if the depth was limited to 4,
> >but I didn't test it long enough to be absolutely certain. So the safest
> >is indeed to blacklist it.
>
> Yes, broken on the Silicon Image controllers for sure.
> But what type of controller did you observe the failures on, Jens ?
achi
--
Jens Axboe
next prev parent reply other threads:[~2007-02-22 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 5:48 [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver Robert Hancock
2007-02-22 6:57 ` Jeff Garzik
2007-02-22 11:32 ` Jens Axboe
2007-02-22 14:41 ` Mark Lord
2007-02-22 15:41 ` Jens Axboe [this message]
2007-02-22 15:04 ` Ask Bjørn Hansen
2007-02-23 0:18 ` Robert Hancock
2007-02-23 0:21 ` Ask Bjørn Hansen
2007-02-23 22:16 ` Jeff Garzik
2007-03-21 7:32 ` Tejun Heo
2007-03-21 12:52 ` Mathieu Bérard
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=20070222154156.GB4740@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--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 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.