From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, ornati@fastwebnet.it
Subject: Re: [PATCH #upstream] libata: blacklist NCQ on Seagate Barracuda ST380817AS
Date: Thu, 04 Oct 2007 21:32:55 +0900 [thread overview]
Message-ID: <4704DD77.6070609@gmail.com> (raw)
In-Reply-To: <20071004125436.1ae8dbe8@the-village.bc.nu>
Alan Cox wrote:
> On Thu, 4 Oct 2007 11:06:56 +0900
> Tejun Heo <htejun@gmail.com> wrote:
>
>> From: Paolo Ornati <ornati@fastwebnet.it>
>>
>> Seagate Barracuda ST380817AS has troubles with NCQ. For example,
>> unpacking a tarball on an XFS filesystem gives this:
>>
>> ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
>> ata1.00: cmd 61/40:00:29:a3:98/00:00:00:00:00/40 tag 0 cdb 0x0 data 32768 out
>> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>
> Looking at this and our NCQ code I don't see any provision for drive
> unfairness in our code. If we continue to issue commands to the drive I'm
> not seeing where we guarantee a given command will ever complete rather
> than being deferred forever by a dumb drive - which some SCSI drives also
> will do...
After several such timeouts, libata will turn off NCQ which should solve
the problem.
--
tejun
next prev parent reply other threads:[~2007-10-04 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 2:06 [PATCH #upstream] libata: blacklist NCQ on Seagate Barracuda ST380817AS Tejun Heo
2007-10-04 11:54 ` Alan Cox
2007-10-04 12:32 ` Tejun Heo [this message]
2007-10-10 1:32 ` 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=4704DD77.6070609@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=ornati@fastwebnet.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;
as well as URLs for NNTP newsgroup(s).