From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: 2.6.27.6 question: ata_sff_hsm_move: ata15 (why always ata15)?
Date: Sun, 16 Nov 2008 15:14:01 +0900 [thread overview]
Message-ID: <491FBA29.3000803@kernel.org> (raw)
In-Reply-To: <20081115103424.34f01370@lxorguk.ukuu.org.uk>
Alan Cox wrote:
> On Fri, 14 Nov 2008 21:22:58 -0600
> Robert Hancock <hancockr@shaw.ca> wrote:
>
>> Justin Piszcz wrote:
>>> I am trying to find out what the root cause of this error/problem is:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=462425
>> The problem is that people assume that timeouts with DRDY like that bug
>> refers to must be the same problem when it is often not
>
> The first stopping point is to apply the DRQ drain patch I sent to the
> list some time ago and is hopefully lined up for 2.6.29. After that point
> you can begin to look at the remaining cases, until then its hardly worth
> it.
Is it really? For many SATA controllers, DRQ draining isn't really
necessary. PATA might be a completely different story tho.
--
tejun
next prev parent reply other threads:[~2008-11-16 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:55 2.6.27.6 question: ata_sff_hsm_move: ata15 (why always ata15)? Justin Piszcz
2008-11-15 0:12 ` Justin Piszcz
2008-11-15 3:22 ` Robert Hancock
2008-11-15 3:22 ` Robert Hancock
2008-11-15 10:34 ` Alan Cox
2008-11-16 6:14 ` Tejun Heo [this message]
2008-11-16 9:11 ` Justin Piszcz
2008-11-16 9:14 ` Tejun Heo
2008-11-16 11:25 ` Alan Cox
2008-11-24 18:20 ` Mark Lord
2008-11-24 18:32 ` Alan Cox
2008-11-25 16:35 ` Mark Lord
2008-11-15 17:39 ` Mario 'BitKoenig' Holbe
2008-11-15 22:00 ` Justin Piszcz
2008-11-15 22:00 ` Justin Piszcz
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=491FBA29.3000803@kernel.org \
--to=tj@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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 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.