From: Mark Lord <kernel@teksavvy.com>
To: Vishal Rao <vishalrao@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
David Rees <drees76@gmail.com>,
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: Wed, 27 Jan 2010 17:44:16 -0500 [thread overview]
Message-ID: <4B60C1C0.8050402@teksavvy.com> (raw)
In-Reply-To: <aacba7e1001261714n42a68824k62c411cd1e5d7893@mail.gmail.com>
Vishal Rao wrote:
> http://pastebin.ubuntu.com/347122/
>
> I'm running Ubuntu Lucid 10.04 alphas at the moment and note that even
> if I "successfully reproduce" the problem on my alternate hardware, its
> still the same particular disk which can't disprove that it's simply a
> single defective piece - the only thing stuck in my mind is Win7rc working
> fine so far while various other Linux distros have exhibited the same problem.
..
The errors in that log indicate bad media.
So the question is, can you demonstrate Win7rc NOT having the same
errors when accessing the SAME (logical) sectors ?
-ml
next prev parent reply other threads:[~2010-01-27 22:44 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 [this message]
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=4B60C1C0.8050402@teksavvy.com \
--to=kernel@teksavvy.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;
as well as URLs for NNTP newsgroup(s).