From: Tejun Heo <htejun@gmail.com>
To: James Ray <j.ray@qmul.ac.uk>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: Bug? ahci.c
Date: Wed, 28 Feb 2007 01:05:24 +0900 [thread overview]
Message-ID: <45E456C4.1050102@gmail.com> (raw)
In-Reply-To: <45E45495.2020800@qmul.ac.uk>
James Ray wrote:
> I managed to get a response from Jeff on the linux-kernel list which I
> have yet to respond to (sorry!).
>
> This problem was fixed by dodgy NCQ on the disk itself, S/N:
> WMANM2828677 P/N: WD1600JS-60MHB1 (Western Digital 160Gb). If I disabled
> the disk it worked fine, or replaced the disks with Some Seagates it
> worked fine also!
>
> I am running a 2.6.19 at the moment quite happily. Still want me to test
> a 2.6.20.1? I might be able to get a bit of time later on this week.
Nope, as long as you're happy. :-)
--
tejun
prev parent reply other threads:[~2007-02-27 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 12:21 Bug? ahci.c James Ray
2007-02-27 15:20 ` Tejun Heo
2007-02-27 15:56 ` James Ray
2007-02-27 16:05 ` Tejun Heo [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=45E456C4.1050102@gmail.com \
--to=htejun@gmail.com \
--cc=j.ray@qmul.ac.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).