From: Tejun Heo <htejun@gmail.com>
To: Massimiliano Hofer <max@nucleus.it>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Florin Iucha <florin@iucha.net>,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: spurious completions during NCQ?
Date: Mon, 18 Jun 2007 14:30:00 +0900 [thread overview]
Message-ID: <46761858.7080208@gmail.com> (raw)
In-Reply-To: <200706150951.58586.max@nucleus.it>
Massimiliano Hofer wrote:
> On Friday 8 June 2007, Alan Cox wrote:
>
>>> Model Number: HITACHI HTS541680J9SA00
>>> Serial Number: SB******I57L4A
>> This one is already blacklisted in the windows drivers.
>
> I have the same problem with this drive (shipped with a Thinkpad Z61m):
>
> Model Number: HITACHI HTS541612J9SA00
> Firmware Revision: SBDIC7JP
>
> It reported several dozen spurious completions over a few days, but I can't
> find any corruption. Is it really dangerous? I understand this clearly is a
> firmware bug, but I'm not sure how to interpret the drive behavior.
> I can perform any test you like, if you find it useful.
It has _slight_ change of being dangerous and is just in violation of
the protocol. No real data corruption case reported yet tho. Till now
most drives which report such problems had stinky NCQ implementation
anyway - slow, buggy, blacklisted in the other OS, etc... I'll submit a
patch to blacklist the drive.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-06-18 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Nigm+GFAuAW+QzfgqTUfmHJoFfU@ifi.uio.no>
2007-06-06 14:28 ` spurious completions during NCQ? Robert Hancock
2007-06-07 12:04 ` Florin Iucha
2007-06-08 12:55 ` Tejun Heo
2007-06-08 13:11 ` Florin Iucha
2007-06-08 13:20 ` [PATCH] libata: disable NCQ for HITACHI HTS541680J9SA00/SB21C7EP Tejun Heo
2007-06-08 15:28 ` Alan Cox
2007-06-10 2:41 ` Jeff Garzik
2007-06-08 15:28 ` spurious completions during NCQ? Alan Cox
2007-06-15 7:51 ` Massimiliano Hofer
2007-06-18 5:30 ` Tejun Heo [this message]
2007-06-06 5:28 Florin Iucha
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=46761858.7080208@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=florin@iucha.net \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=max@nucleus.it \
/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