From: Jarod Wilson <jarod@wilsonet.com>
To: Vishal Rao <vishalrao@gmail.com>
Cc: David Rees <drees76@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, trivial@kernel.org,
stable@kernel.org
Subject: Re: [PATCH] ata: Disable NCQ for Crucial M225 brand SSDs
Date: Thu, 28 Jan 2010 15:12:07 -0500 [thread overview]
Message-ID: <be3a4a1001281212h73ba1bd5ja8e275679f3554d7@mail.gmail.com> (raw)
In-Reply-To: <aacba7e1001270814s3ebdcc62i39d6ed0efeb194eb@mail.gmail.com>
On Wed, Jan 27, 2010 at 11:14 AM, Vishal Rao <vishalrao@gmail.com> wrote:
> 2010/1/27 Jarod Wilson <jarod@wilsonet.com>:
>> How to define a group gets... Messy. Just as a data point, my own
>> Barefoot-based SSD, an OCZ Vertex, has no NCQ-related problems
>> whatsoever, so far as I know. Its currently hooked to a Zotac ION
>> board, which has ahci-driven sata controllers of some sort, was
>> previously in a Dell Studio Hybrid, where it also worked just fine.
>
> Thanks for data point. I'm personally hoping for other Crucial users
> specifically.
>
> Is NCQ enabled - if you grep dmesg for ata ?
$ dmesg | grep -i ncq
ahci 0000:00:0b.0: flags: 64bit ncq sntf led pmp pio slum part sxs
ata1.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> The kernel already appears to blacklist (disable NCQ for) OCZ
> SSD models with firmware version "02.10104".
Here's what I've got:
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-7: OCZ-VERTEX 1275, 00.P97, max UDMA/133
ata1.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA OCZ-VERTEX 1275 00.P PQ: 0 ANSI: 5
--
Jarod Wilson
jarod@wilsonet.com
next prev parent reply other threads:[~2010-01-28 20:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 15:04 Vishal Rao
2010-01-26 16:02 ` Alan Cox
2010-01-26 16:19 ` Vishal Rao
2010-01-26 20:27 ` Willy Tarreau
2010-01-26 20:51 ` David Rees
2010-01-27 0:21 ` Vishal Rao
2010-01-27 0:32 ` David Rees
2010-01-27 0:49 ` Vishal Rao
2010-01-27 1:02 ` Alan Cox
2010-01-27 1:14 ` Vishal Rao
2010-01-27 22:44 ` Mark Lord
2010-01-27 23:16 ` Vishal Rao
2010-01-27 23:41 ` David Rees
2010-01-28 0:24 ` Vishal Rao
2010-01-28 2:12 ` Vishal Rao
2010-01-27 15:39 ` Jarod Wilson
2010-01-27 16:14 ` Vishal Rao
2010-01-28 20:12 ` Jarod Wilson [this message]
2010-01-26 21:46 ` Jeff Garzik
2010-01-27 0:24 ` Vishal Rao
2010-01-27 2:23 ` Mark Lord
2010-01-27 5:36 ` Vishal Rao
2010-01-27 12:15 ` Vishal Rao
2010-01-27 22:49 ` Mark Lord
2010-01-29 3:56 ` Mark Lord
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=be3a4a1001281212h73ba1bd5ja8e275679f3554d7@mail.gmail.com \
--to=jarod@wilsonet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drees76@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=trivial@kernel.org \
--cc=vishalrao@gmail.com \
/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
all inboxes | Powered by JetHome®