From: Paolo Ornati <ornati@fastwebnet.it>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
Date: Sun, 30 Sep 2007 16:46:10 +0200 [thread overview]
Message-ID: <20070930164610.20818867@localhost> (raw)
In-Reply-To: <20070930152908.1f58d39d@the-village.bc.nu>
On Sun, 30 Sep 2007 15:29:08 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > 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)
>
> What makes you sure that is an NCQ problem ?
It goes away with:
echo 1 > /sys/block/sda/device/queue_depth
I have this problem only with XFS, and even with XFS it goes away
mounting with "nobarrier"...
--
Paolo Ornati
Linux 2.6.23-rc8-ga64314e6-dirty on x86_64
next prev parent reply other threads:[~2007-09-30 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070930160548.235be972@localhost>
[not found] ` <46FFAFE1.2010302@gmail.com>
2007-09-30 14:42 ` [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS Paolo Ornati
[not found] ` <20070930152908.1f58d39d@the-village.bc.nu>
2007-09-30 14:46 ` Paolo Ornati [this message]
2007-09-30 15:05 ` Jeff Garzik
2007-09-30 15:28 ` Paolo Ornati
2007-09-30 15:43 ` Jeff Garzik
2007-09-30 15:52 ` Paolo Ornati
2007-09-30 15:59 ` Jeff Garzik
2007-09-30 16:03 ` Paolo Ornati
2007-09-30 17:26 ` Mark Lord
2007-09-30 17:29 ` Tejun Heo
2007-09-30 17:43 ` Mark Lord
2007-09-30 17:51 ` Tejun Heo
2007-09-30 18:54 ` Mark Lord
2007-09-30 19:01 ` Mark Lord
2007-10-02 9:19 ` Tejun Heo
2007-10-02 15:40 ` Paolo Ornati
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=20070930164610.20818867@localhost \
--to=ornati@fastwebnet.it \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--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 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).