From: Mark Lord <mlord@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Ric Wheeler <ric@emc.com>, Linux-ide <linux-ide@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: faulty disk testing
Date: Tue, 05 Sep 2006 10:15:30 -0400 [thread overview]
Message-ID: <44FD8682.1070305@pobox.com> (raw)
In-Reply-To: <44FD84E8.8000705@gmail.com>
ata_port_wait_eh
Tejun Heo wrote:
> ..
> For Ric's case, I'm waiting for more info. If EH is looping forever
> without reporting to upper layer, it definitely needs fixing, but I
> don't think that's the case.
What happens with the loop in ata_port_wait_eh() for a drive
which never succeeds in the reset/reinit phase?
Cheers
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
next prev parent reply other threads:[~2006-09-05 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 1:30 faulty disk testing Ric Wheeler
2006-09-05 11:57 ` Tejun Heo
2006-09-05 12:46 ` Ric Wheeler
2006-09-05 13:48 ` Mark Lord
2006-09-05 14:08 ` Tejun Heo
2006-09-05 14:15 ` Mark Lord [this message]
2006-09-05 14:45 ` Tejun Heo
2006-09-05 14:19 ` Ric Wheeler
2006-09-05 14:56 ` Tejun Heo
2006-09-05 15:48 ` Ric Wheeler
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=44FD8682.1070305@pobox.com \
--to=mlord@pobox.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=ric@emc.com \
/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).