From: Jeff Garzik <jeff@garzik.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Alan <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] libata: add another Maxtor drive with broken NCQ to the list
Date: Thu, 12 Jul 2007 14:39:28 -0400 [thread overview]
Message-ID: <46967560.6020007@garzik.org> (raw)
In-Reply-To: <469674DF.9000804@redhat.com>
Chuck Ebbert wrote:
> Add another Maxtor 6B200M0 drive with broken NCQ to the list.
>
> Signed-off-by: Chuck Ebbert <cebbert@redhat.com>
> ---
> drivers/ata/libata-core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-2.6.22.noarch.orig/drivers/ata/libata-core.c
> +++ linux-2.6.22.noarch/drivers/ata/libata-core.c
> @@ -3787,6 +3787,7 @@ static const struct ata_blacklist_entry
> { "FUJITSU MHT2060BH", NULL, ATA_HORKAGE_NONCQ },
> /* NCQ is broken */
> { "Maxtor 6L250S0", "BANC1G10", ATA_HORKAGE_NONCQ },
> + { "Maxtor 6B200M0", "BANC1BM0", ATA_HORKAGE_NONCQ },
> { "Maxtor 6B200M0", "BANC1B10", ATA_HORKAGE_NONCQ },
> /* NCQ hard hangs device under heavier load, needs hard power cycle */
> { "Maxtor 6B250S0", "BANC1B70", ATA_HORKAGE_NONCQ },
Alan Cox posted some example code recently, which demonstrated how to
add support for wildcards to the ATA blacklist.
Would you be willing to grab or recreate that, and then simply blacklist
"BANC*"
Jeff
next prev parent reply other threads:[~2007-07-12 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 18:37 [PATCH] libata: add another Maxtor drive with broken NCQ to the list Chuck Ebbert
2007-07-12 18:39 ` Jeff Garzik [this message]
2007-07-12 19:03 ` Chuck Ebbert
2007-07-12 20:10 ` Jeff Garzik
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=46967560.6020007@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).