From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <mlord@pobox.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Mark Lord <liml@rtr.ca>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
hare@suse.de
Subject: Re: libata total system lockup fix
Date: Fri, 12 Aug 2005 11:38:00 +0900 [thread overview]
Message-ID: <42FC0B88.4060404@gmail.com> (raw)
In-Reply-To: <42FC07EF.9060506@pobox.com>
Mark Lord wrote:
> Tejun Heo wrote:
>
>>
>> * _All_ errors are handled in EH thread.
>> * Once any error has occurred, all normal processing stops until
>> error condition is cleared by EH.
>
>
> Do you mean "all normal processing" for that channel stops,
> or *ALL* processing on all libata channels stops?
>
> Obviously the former, I presume.
>
> Cheers
Yeah, the former of course. ;-) Error state is indicated by one of
the followings.
* ATA_FLAG_ERROR : one or more errors have occurred and EH is
scheduled to run.
* ATA_FLAG_RECOVERY : EH in progress
When either of above flags is set, only commands w/ ATA_QCFLAG_PREEMPT
flag set gets to run and complete. So, currently, sense requesting and
NCQ log page reading are done w/ the flag set.
--
tejun
next prev parent reply other threads:[~2005-08-12 2:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 13:47 libata total system lockup fix Mark Lord
2005-07-25 14:51 ` Jeff Garzik
2005-07-25 15:53 ` Mark Lord
2005-08-05 3:52 ` Tejun Heo
2005-08-05 4:01 ` Tejun Heo
2005-08-11 20:13 ` Jeff Garzik
2005-08-12 0:49 ` Tejun Heo
2005-08-12 2:22 ` Mark Lord
2005-08-12 2:38 ` Tejun Heo [this message]
2005-08-12 2:41 ` Tejun Heo
2005-08-09 15:16 ` Mark Lord
2005-08-09 23:54 ` Tejun Heo
2005-08-10 14:16 ` Mark Lord
2005-08-10 21:24 ` Jeff Garzik
2005-08-19 0:46 ` Mark Lord
2005-08-19 3:21 ` Tejun Heo
2005-08-19 3:36 ` Mark Lord
2005-08-19 3:45 ` Tejun Heo
2005-08-19 4:01 ` Mark Lord
2005-08-19 9:37 ` Erik Slagter
2005-08-19 9:35 ` Erik Slagter
2005-08-19 13:07 ` Mark Lord
2005-08-19 13:32 ` Bartlomiej Zolnierkiewicz
2005-08-19 13:37 ` Bartlomiej Zolnierkiewicz
2005-09-03 22:58 ` Mark Lord
2005-09-03 23:06 ` Jeff Garzik
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=42FC0B88.4060404@gmail.com \
--to=htejun@gmail.com \
--cc=hare@suse.de \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.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.