From: Vishal Rao <vishalrao@gmail.com>
To: Mark Lord <kernel@teksavvy.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: Wed, 27 Jan 2010 11:06:13 +0530 [thread overview]
Message-ID: <aacba7e1001262136o3b1cfb97yed421bba02580bef@mail.gmail.com> (raw)
In-Reply-To: <4B5FA38A.5040700@teksavvy.com>
2010/1/27 Mark Lord <kernel@teksavvy.com>:
> 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?
Thanks for taking the time on this.
I am unsure of the "specific IndiLinx firmware build number" though I've
noticed the release numbers are common for different manufacturers.
For example my disk came with the then-latest firmware "1819"
(with TRIM) which had write-perf issues then they recently released
"1916" which added TRIM and GC support (seems to work very well
I should say).
Linux logs "CRUCIAL_CT128M225" and "1916" in my dmesg, speaking
of which, here is my latest full dmesg: http://pastebin.ubuntu.com/363659/
And here is the output of hdparm --Istdout /dev/sd? :
http://pastebin.ubuntu.com/363660/
I am running the following on Kubuntu development version, uname -a is:
"Linux thunderbird 2.6.32-11-generic #16~vishalrao2 SMP Tue Jan 26
19:03:33 IST 2010 x86_64 GNU/Linux"
The " ~vishalrao2 " portion indicating it being the proposed patch -
in that good old "works for me" kind of way.
next prev parent reply other threads:[~2010-01-27 5:36 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
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 [this message]
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=aacba7e1001262136o3b1cfb97yed421bba02580bef@mail.gmail.com \
--to=vishalrao@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=trivial@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 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®