From: Robert Hancock <hancockr@shaw.ca>
To: linux-ide@vger.kernel.org
Cc: jgarzik@pobox.com
Subject: Re: [PATCH] libata: blacklist NCQ on OCZ CORE 2 SSD
Date: Mon, 15 Dec 2008 18:36:43 -0600 [thread overview]
Message-ID: <4946F81B.7020408@shaw.ca> (raw)
In-Reply-To: <4946C96B.2030603@dsrg.mff.cuni.cz>
Lubomír Bulej wrote:
> Hello,
>
> after putting a 250G OCZ CORE v2 SSD into my notebook, I have to endure
> several invocations of the ata EH before the kernel decides to disable
> NCQ due too many errors. The drive reports NCQ of depth 1, which is
> probably useless anyway.
>
> The patchlet below saves me the waiting for the completion of several
> ata EH invocations, but I'm not sure if this is the right solution.
> Attached are two dmesg dumps, one with errors and the other with the
> patchlet compiled in. Attached is also "hdparm -I" of the drive.
I suspect it's all we can really do. NCQ depth of 1 isn't entirely
useless, as using NCQ commands still allows the drive to send/request
data for an individual request out of order, which NCQ commands don't
allow. However, in this case it would appear that the device is sending
back a bogus all-zeros FIS to the controller which triggers error handling.
The "applying bridge limits" part is interesting, that would imply the
device's identify data doesn't properly indicate it's actually a SATA
device so the kernel assumes it's a PATA device behind a SATA bridge. I
don't think it's related to the problem but it does suggest that whoever
designed the SATA interface on that thing probably didn't do a ton of
validation on it..
next prev parent reply other threads:[~2008-12-16 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 21:17 [PATCH] libata: blacklist NCQ on OCZ CORE 2 SSD Lubomír Bulej
2008-12-16 0:36 ` Robert Hancock [this message]
[not found] ` <49476EC7.5080201@dsrg.mff.cuni.cz>
2008-12-17 1:04 ` Robert Hancock
2008-12-22 8:14 ` Tejun Heo
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=4946F81B.7020408@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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.