From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
lethalwp@scarlet.be, Luke Macken <lmacken@redhat.com>
Subject: Re: [PATCH upstream-fixes] libata: disable NCQ on Crucial C300 SSD
Date: Tue, 06 Apr 2010 10:57:28 -0400 [thread overview]
Message-ID: <4BBB4BD8.4050604@garzik.org> (raw)
In-Reply-To: <4BB9421E.9050007@kernel.org>
On 04/04/2010 09:51 PM, Tejun Heo wrote:
> Crucial said,
>
> Thank you for contacting us. We know that with our M225 line of SSDs
> you sometimes need to disable NCQ (native command queuing) to avoid
> just the type of errors you're seeing. Our recommendation for the
> M225 is to add libata.force=noncq to your Linux kernel boot options,
> under the kernel ATA library option.
>
> I have sent your feedback to the engineers working on the C300, and
> asked them to please pass it on to the firmware team. I have been
> notified that they are in the process of testing and finalizing a
> new firmware version, that you can expect to see released around the
> end of April. We’ll keep you posted as to when it will be available
> for download.
>
> So, turn off NCQ on the drive w/ the current firmware revision.
>
> Reported in the following bug.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=15573
>
> Signed-off-by: Tejun Heo<tj@kernel.org>
> Reported-by: lethalwp@scarlet.be
> Reported-by: Luke Macken<lmacken@redhat.com>
> ---
> drivers/ata/libata-core.c | 3 +++
> 1 file changed, 3 insertions(+)
applied
prev parent reply other threads:[~2010-04-06 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 1:51 [PATCH upstream-fixes] libata: disable NCQ on Crucial C300 SSD Tejun Heo
2010-04-06 14:57 ` Jeff Garzik [this message]
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=4BBB4BD8.4050604@garzik.org \
--to=jeff@garzik.org \
--cc=lethalwp@scarlet.be \
--cc=linux-ide@vger.kernel.org \
--cc=lmacken@redhat.com \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.