From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Jens Axboe <axboe@suse.de>, Ric Wheeler <ric@emc.com>
Subject: Re: libata EH appears to be NFG up to 2.6.17 (at least).
Date: Sun, 09 Jul 2006 01:56:12 +0900 [thread overview]
Message-ID: <44AFE3AC.9030709@gmail.com> (raw)
In-Reply-To: <44AE5BA1.6000409@rtr.ca>
Hello, Mark Lord.
Mark Lord wrote:
[--snip--]
> I dunno what the new EH does (yet), but the only good way to deal with this
> is for the ATA status & error values to be read *and* saved on command
> completion,
> and then reused by any later code that needs to do detailed sense reporting
> or other diagnostics.
Yeap, this is exactly what new EH does. It stores TF in qc->result_tf
on failure and EH/SCSI completion only uses the cached TF stored at the
time of failure.
> With NCQ/TCQ, this can be tough to achieve, possibly requiring the LLDD
> to drop to legacy mode on error, and capture the values there. Of
> course, by then
> it's too late to be perfect, as the host controller has probably already
> read
> and discarded the drive status at least once. (the PDC sata_qstor device
> is an exception there -- they save/return failed status during queuing).
With NCQ, the true TF is retrieved via log page 10. EH retrieves it and
stores it in qc->result_tf. The rest is the same.
With PMP, things get more interesting though. :-(
--
tejun
prev parent reply other threads:[~2006-07-08 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 20:37 libata EH appears to be NFG up to 2.6.17 (at least) Mark Lord
2006-07-06 20:47 ` Jeff Garzik
2006-07-06 20:51 ` Mark Lord
2006-07-06 21:24 ` Mark Lord
2006-07-06 22:09 ` Jeff Garzik
2006-07-06 23:22 ` Ric Wheeler
2006-07-07 13:03 ` Mark Lord
2006-07-08 16:56 ` 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=44AFE3AC.9030709@gmail.com \
--to=htejun@gmail.com \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--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 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.