From: Charles Shannon Hendrix <shannon@widomaker.com>
To: linux-kernel@vger.kernel.org
Subject: sata_nv: 2.6.22 is not fixed, but certainly improved
Date: Mon, 16 Jul 2007 19:55:22 -0400 [thread overview]
Message-ID: <20070716195522.5ea906ea@daydream> (raw)
I just compiled 2.6.22.1 on my Kubuntu 7.0.4 system.
As before, I get errors using my Seagate SATA drives, and setting adma=0
fixes the problem. I've posted the exact error/reset messages several times
before.
However, I would like to note that it happens far less often with 2.6.22.1
than it did with 2.6.21.
The history on my own machine is like this:
2.6.19 perfect, but of course no ADMA/NCQ
2.6.20 horrible, with hard resets starting immediately upon
boot, and taking 15 minutes to finally disable NCQ
2.6.21 bad resets, but they only occured ever 10-30 minutes,
NCQ never disabled
2 6.22 resets infrequent, they are soft resets, and much
quicker than before (i.e. less interruption of my usage)
NCQ is never disabled
I have no idea why I might be seeing a gradual reduction in the severity of
the problem, but it seems worth noting.
I want to point it out in case it means something to anyone working on
the kernel, especially the SATA code and drivers.
In the last 4 hours of use, I've seen a single reset.
On all previous kernels under the same load, I'd already have seen several of
them, or with 2.6.20, a constant stream of them.
--
shannon | An Irishman is never drunk as long as he can hold onto
| one blade of grass and not fall off the face of the earth.
next reply other threads:[~2007-07-16 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 23:55 Charles Shannon Hendrix [this message]
[not found] <fa.9GsXANcxdaaxd0tpVuOSy0KKiew@ifi.uio.no>
2007-07-17 1:07 ` sata_nv: 2.6.22 is not fixed, but certainly improved Robert Hancock
[not found] <fa.zmoY2vXgUq7eREE2Ed2QLHUKvsI@ifi.uio.no>
[not found] ` <fa.Y7u9A1ShoS8YDBp6YOFkRHtg2K0@ifi.uio.no>
2007-07-17 6:08 ` Robert Hancock
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=20070716195522.5ea906ea@daydream \
--to=shannon@widomaker.com \
--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