From: Robert Hancock <hancockr@shaw.ca>
To: Chuck Short <zulcss@ubuntu.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/7] ata: blacklist FUJITSU MHW2160BH PL
Date: Mon, 21 Jul 2008 13:21:51 -0600 [thread overview]
Message-ID: <4884E1CF.2060405@shaw.ca> (raw)
In-Reply-To: <fa.DCjHMBBwNh4jCV7S5sRgLaXPnZo@ifi.uio.no>
Chuck Short wrote:
> Reference: https://launchpad.net/bugs/175834
>
> CC: linux-ide@vger.kernel.org
> Signed-off-by: Chuck Short <zulcss@ubuntu.com>
> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
> Signed-off-by: Ben Collins <ben.collins@canonical.com>
> ---
> drivers/ata/libata-core.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 9bef1a8..2664082 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -3935,6 +3935,7 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
> { "HTS541060G9SA00", "MB3OC60D", ATA_HORKAGE_NONCQ, },
> { "HTS541080G9SA00", "MB4OC60D", ATA_HORKAGE_NONCQ, },
> { "HTS541010G9SA00", "MBZOC60D", ATA_HORKAGE_NONCQ, },
> + { "FUJITSU MHW2160BH PL", "0084001E", ATA_HORKAGE_NONCQ, },
>
> /* devices which puke on READ_NATIVE_MAX */
> { "HDS724040KLSA80", "KFAOA20N", ATA_HORKAGE_BROKEN_HPA, },
NACK, this report is based on spurious NCQ completions in ahci which
were found to be bogus and the detection was removed in later kernels.
next parent reply other threads:[~2008-07-21 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ALyrA5g+KD/4GlXdcY53hIWqKUs@ifi.uio.no>
[not found] ` <fa.DCjHMBBwNh4jCV7S5sRgLaXPnZo@ifi.uio.no>
2008-07-21 19:21 ` Robert Hancock [this message]
[not found] <24762.90.138.930.038.1036103001.ben.collins@canonical.com>
2008-01-18 18:21 ` [PATCH 2/7] ata: blacklist FUJITSU MHW2160BH PL Chuck Short
2008-07-31 5:45 ` 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=4884E1CF.2060405@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zulcss@ubuntu.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 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).