From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Date: Fri, 16 Mar 2007 07:56:33 -0600 [thread overview]
Message-ID: <45FAA211.5030402@shaw.ca> (raw)
In-Reply-To: <fa.wBi/iM3CKSfrll7UnPHTbU0scEQ@ifi.uio.no>
(linux-ide cc'ed)
Max Kellermann wrote:
> Hi,
>
> I have been trying to upgrade my 2.6.19 kernel for a while now,
> without success. All kernel versions since 2.6.20 failed with a
> timeout while trying to write to my SATA hard disk. After I wait for
> a while (during which all I/O to the hard disk blocks), the kernel
> message "NCQ disabled due to excessive errors" appears, and the system
> seems to work perfectly.
>
> My system is an Athlon64 X2 on an Asus A8N-Premium. I'm using the
> sata_nv driver for the on-board SATA controller. My only hard disk is
> a Samsum HD401LJ (400 GB).
>
> The kernel is build statically, and the only module is nvidia.ko. If
> someone believes it may make a difference, I can try the kernel
> without the proprietary module.
>
> Please see the kernel config and dmesg attached to this email.
>
> I don't know the libata subsystem well, but I suspect my hard drive
> has to be added to the NCQ blacklist.
>
> Max
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
parent reply other threads:[~2007-03-16 13:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <fa.wBi/iM3CKSfrll7UnPHTbU0scEQ@ifi.uio.no>]
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=45FAA211.5030402@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--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).