From: Robert Hancock <hancockr@shaw.ca>
To: "Lubomír Bulej" <lubomir.bulej@dsrg.mff.cuni.cz>
Cc: jgarzik@pobox.com, ide <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata: blacklist NCQ on OCZ CORE 2 SSD
Date: Tue, 16 Dec 2008 19:04:29 -0600 [thread overview]
Message-ID: <4948501D.50000@shaw.ca> (raw)
In-Reply-To: <49476EC7.5080201@dsrg.mff.cuni.cz>
Lubomír Bulej wrote:
> Hello,
>
> thanks for the insight - I can only (somewhat) parse the simplest of ATA
> errors related to bad sectors :-)
>
>> 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..
>
> It well may be, who knows - there is basically no detailed info on the
> product. Is there a way to find out, apart from taking it apart and
> taking a peek at the chips? :-)
Likely not, but it seems pretty much impossible that it is, if it
reports NCQ support..
>
> BTW, can the kernel assumption of "pata-behind-sata-bridge" cause any
> problems?
It looks like all that does is limit the transfer rate to UDMA5 (which
doesn't actually make any difference if it's really SATA) and limits
maximum sectors per transfer to 200.
>
> Anyway, I guess that's what we get when memory manufacturers (let's say
> assemblers) start delving into persistent storage. I was a bit dazed by
> the "oh so distinguishing" model name/number...
>
>
> Best regards,
> Lubomir
>
>
next prev parent reply other threads:[~2008-12-17 1:04 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
[not found] ` <49476EC7.5080201@dsrg.mff.cuni.cz>
2008-12-17 1:04 ` Robert Hancock [this message]
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=4948501D.50000@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=lubomir.bulej@dsrg.mff.cuni.cz \
/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).