From: Don Mullis <dwm@meer.net>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Hitachi disk: spurious completions during NCQ
Date: Sun, 14 Oct 2007 23:07:51 -0700 [thread overview]
Message-ID: <87zlyksyfc.fsf@meer.net> (raw)
In-Reply-To: <9cP6K-6rV-29@gated-at.bofh.it> (Luca Tettamanti's message of "Wed\, 10 Oct 2007 21\:10\:22 +0200")
> ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd FIS=005040a1:00020000
> ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out
> res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation)
This has been seen with several Hitachi drives. There's speculation
that it's due to a bug in the drive firmware:
http://groups.google.it/group/linux.kernel/browse_thread/thread/a4bd3c19565a2009/389817602f0cd551?hl=it&lnk=st&q=hitachi+hsm+violation&rnum=3#389817602f0cd551
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/137470
A workaround:
Index: /etc/rc.local
===================================================================
--- .orig/etc/rc.local 2007-10-13 14:57:10.000000000 -0700
+++ /etc/rc.local 2007-10-13 14:59:21.000000000 -0700
@@ -11,4 +11,7 @@
#
# By default this script does nothing.
+# See https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/137470/
+echo 1 > /sys/block/sda/device/queue_depth
+
exit 0
next parent reply other threads:[~2007-10-15 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9cP6K-6rV-29@gated-at.bofh.it>
2007-10-15 6:07 ` Don Mullis [this message]
2007-10-15 9:47 ` Hitachi disk: spurious completions during NCQ Luca
2007-10-10 19:03 Luca Tettamanti
2007-10-13 0:46 ` Andrew Morton
2007-10-13 16:13 ` Luca
2007-10-13 16:13 ` Luca
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=87zlyksyfc.fsf@meer.net \
--to=dwm@meer.net \
--cc=kronos.it@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.