From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Frequent SATA resets with sata_nv (fwd)
Date: Sun, 24 Jun 2007 18:09:29 +0100 [thread overview]
Message-ID: <200706241809.29449.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <alpine.DEB.0.99.0706232051520.31644@cheetah.fastcat.org>
(Sorry, accidentally dropped LKML)
On Sunday 24 June 2007 01:52:30 you wrote:
> Googling around lkml.org, I found a few threads investigating what look
> like very similar problems, some of which never seemed to find the
> solution, but one of which came up with a fairly quick answer it seemed,
> namely that the drive's NCQ implementation was horked:
> http://lkml.org/lkml/2007/4/18/32
Well, there's been generic problems with the ADMA code on the CK804, but I
think Robert fixed them (added CC). I've certainly had NO problems since
2.6.21.
However, assuming the drive's NCQ _is_ busted and needs to be blacklisted, you
might find you can temporarily work around the problem by loading the sata_nv
module with adma=0, or boot with sata_nv.adma=0. Not to point the finger at
ADMA support specifically, of course, but simply that ADMA enables the NCQ
features.
It'd be good if you could report back whether this helps fix it.
> While I don't have older logs to verify exactly when this started, it
> was fairly recent, perhaps around my 2.6.20.1 to 2.6.21.1 kernel
> upgrade.
Yes, this is probably around the time adma became the default.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2007-06-24 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 0:52 Frequent SATA resets with sata_nv (fwd) Matthew "Cheetah" Gabeler-Lee
2007-06-24 17:09 ` Alistair John Strachan [this message]
[not found] <fa.Z5bo5y2TvW4efa6slAJpcdPwqAA@ifi.uio.no>
2007-06-24 19:53 ` Robert Hancock
2007-06-26 16:06 ` Matthew "Cheetah" Gabeler-Lee
2007-06-26 17:29 ` Heinz Ulrich Stille
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=200706241809.29449.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).