From: David Rees <drees76@gmail.com>
To: Vishal Rao <vishalrao@gmail.com>
Cc: 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: Tue, 26 Jan 2010 16:32:49 -0800 [thread overview]
Message-ID: <72dbd3151001261632t7bbe43d0nb7490eae02185c81@mail.gmail.com> (raw)
In-Reply-To: <aacba7e1001261621v6abb4270i996a28d19c9f7d7@mail.gmail.com>
On Tue, Jan 26, 2010 at 4:21 PM, Vishal Rao <vishalrao@gmail.com> wrote:
> 2010/1/27 David Rees <drees76@gmail.com>:
>> Have there been any other reports of NCQ issues with similar Crucial
>> drives or Indilinx?
>
> I haven't personally seen reports of NCQ specific issues. I have seen
> people (online) reporting "issues" with Linux distro installations
> hanging/freezing etc. and some prior attempts at SMART fixes which
> I also initially tried but did not work for me.
>
> I have tried to "publicise" this issue (forum, blog, mailing list posts)
> in the hope more users may search and identify the correct issue
> so that it may be better verified.
See, that's just the problem. I'm running couple OCZ SSD with an
Indilinx controller and also know that Mark Lord and a bunch of others
are also running them on Linux without issues. And supposedly all the
Indilinx firmware for the different resellers are based on the same
base firmware.
I did have an issue with one of them on a particular motherboard
locking up, but it turned out that the whole SATA controller was flaky
and went away after I replaced the motherboard.
So my concern is that you're proposing to black list NCQ for all users
of those particular models of SSD when it's more likely at this point
that it's a problem with your specific setup.
-Dave
next prev parent reply other threads:[~2010-01-27 0:33 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 [this message]
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=72dbd3151001261632t7bbe43d0nb7490eae02185c81@mail.gmail.com \
--to=drees76@gmail.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
all inboxes | Powered by JetHome®