From: Vishal Rao <vishalrao@gmail.com>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org, vishalrao@gmail.com,
linux-kernel@vger.kernel.org, trivial@kernel.org,
stable@kernel.org
Subject: [PATCH] ata: Disable NCQ for Crucial M225 brand SSDs
Date: Tue, 26 Jan 2010 20:34:31 +0530 [thread overview]
Message-ID: <aacba7e1001260704m27c99a0dy6c3f50c38ce6b430@mail.gmail.com> (raw)
Disable NCQ usage for Crucial M225 model range of SSDs.
Signed-off-by: Vishal Rao <vishalrao@gmail.com>
Tested-by: Vishal Rao <vishalrao@gmail.com>
Cc: stable@kernel.org
---
Should work with 64, 128 (tested) and 256 GB capacities with any
firmware versions in
drivers/ata/libata-core.c because of ATA errors in dmesg, hangs and
filesystem corruption.
The diff is against linux kernel 2.6.33 rc5 though also meant for
2.6.32 stable series due to multiple distros' proposed long term support.
I've tested on my PC with my Crucial M225 model 128 GB SSD and it works
without the need to specify kernel boot option " libata.force=noncq ".
--- linux-source-2.6.33rc5/drivers/ata/libata-core.c.orig 2010-01-26
08:35:54.117306573 +0530
+++ linux-source-2.6.33rc5/drivers/ata/libata-core.c 2010-01-26
08:35:13.047306938 +0530
@@ -4274,6 +4274,9 @@ static const struct ata_blacklist_entry
{ "ST380817AS", "3.42", ATA_HORKAGE_NONCQ },
{ "ST3160023AS", "3.42", ATA_HORKAGE_NONCQ },
{ "OCZ CORE_SSD", "02.10104", ATA_HORKAGE_NONCQ },
+ { "CRUCIAL_CT64M225", NULL, ATA_HORKAGE_NONCQ },
+ { "CRUCIAL_CT128M225", NULL, ATA_HORKAGE_NONCQ },
+ { "CRUCIAL_CT256M225", NULL, ATA_HORKAGE_NONCQ },
/* Seagate NCQ + FLUSH CACHE firmware bug */
{ "ST31500341AS", "SD15", ATA_HORKAGE_NONCQ |
--
"Thou shalt not follow the null pointer for at its end madness and chaos lie."
next reply other threads:[~2010-01-26 15:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 15:04 Vishal Rao [this message]
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
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=aacba7e1001260704m27c99a0dy6c3f50c38ce6b430@mail.gmail.com \
--to=vishalrao@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 \
/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®