From: Mark Lord <kernel@teksavvy.com>
To: Vishal Rao <vishalrao@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
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: Tue, 26 Jan 2010 21:23:06 -0500 [thread overview]
Message-ID: <4B5FA38A.5040700@teksavvy.com> (raw)
In-Reply-To: <aacba7e1001261624m4358e4ebwcf8e2305b0c5fc16@mail.gmail.com>
Vishal Rao wrote:
> 2010/1/27 Jeff Garzik <jgarzik@pobox.com>:
>> On 01/26/2010 11:19 AM, Vishal Rao wrote:
>>> 2010/1/26 Alan Cox<alan@lxorguk.ukuu.org.uk>:
>>>> What controllers did you test with ?
>>> Tested with my own Crucial CT128M225 model which has the IndiLinx
>>> Barefoot controller.
>> By controller, I think Alan meant the host controller (ata_piix, ahci,
>> etc.)?
>
> Oh I see, I have an Intel DP35DP motherboard with onboard IDE controller
> with AHCI enabled. I hope thats sufficient information for now. I did read
> that simply setting the mode to legacy IDE would disable NCQ there but
> would disable for all drives connected.
>
> Please let me know if further info/log files (dmesg, lspci etc) would help
> and I will pastebin them...
..
Can you identify the specific Indilinx build number that your drive firmware
is based upon? If not, then at least post the identify data for us to examine:
hdparm --Istdout /dev/sd?
-ml
next prev parent reply other threads:[~2010-01-27 2:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 15:04 [PATCH] ata: Disable NCQ for Crucial M225 brand SSDs 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
2010-01-26 21:46 ` Jeff Garzik
2010-01-27 0:24 ` Vishal Rao
2010-01-27 2:23 ` Mark Lord [this message]
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=4B5FA38A.5040700@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).