From: Robert Hancock <hancockrwd@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Mark Lord <liml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
Chuck Ebbert <cebbert@redhat.com>,
linux-ide@vger.kernel.org
Subject: Re: libata timeouts when stressing a Samsung HDD
Date: Thu, 19 Feb 2009 20:52:09 -0600 [thread overview]
Message-ID: <499E1AD9.9020904@gmail.com> (raw)
In-Reply-To: <499DFA33.8090009@kernel.org>
Tejun Heo wrote:
> Mark Lord wrote:
>>> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
>>> ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>>> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>>> ata1.00: status: { DRDY }
>>>>> I wonder if it's just a case of too short a timeout on the cache
>>>>> flushes?
>> ..
>>> However, in this case the drive is not reporting Busy status at the
>>> timeout, which suggests maybe an interrupt got lost or something.
>>> (Could be still the drive's fault.)
>> ..
>>
>> If I recall correctly, The reported shadow register contents are bogus
>> when a timeout occurs. So we don't actually know what the drive state was.
>>
>> Or do we, Tejun?
>
> Yeah, it's bogus. Maybe we should just report zeros.
Didn't know that. Shouldn't we be able to do a qc_fill_rtf before error
handling in this case? That would make it easier to tell if we lost an
interrupt or if the drive is just taking too long..
next prev parent reply other threads:[~2009-02-20 2:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 21:40 libata timeouts when stressing a Samsung HDD Chuck Ebbert
2009-02-11 1:30 ` Tejun Heo
2009-02-11 4:08 ` Mark Lord
2009-02-11 20:29 ` Chuck Ebbert
2009-02-11 22:03 ` Mark Lord
2009-02-11 22:11 ` Jeff Garzik
2009-02-11 22:29 ` Mark Lord
2009-02-11 22:54 ` Chuck Ebbert
2009-02-12 16:10 ` Mark Lord
2009-02-12 16:13 ` Mark Lord
2009-02-16 3:12 ` Tejun Heo
2009-02-16 21:30 ` Chuck Ebbert
2009-02-19 6:21 ` Tejun Heo
2009-02-19 16:41 ` Greg Freemyer
2009-02-20 0:33 ` Tejun Heo
2009-02-12 4:28 ` Robert Hancock
2009-02-19 15:27 ` Mark Lord
2009-02-20 0:32 ` Tejun Heo
2009-02-20 2:52 ` Robert Hancock [this message]
2009-02-20 3:26 ` Tejun Heo
2009-03-01 19:31 ` Robert Hancock
2009-03-01 20:28 ` Alan Cox
2009-02-11 20:24 ` Chuck Ebbert
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=499E1AD9.9020904@gmail.com \
--to=hancockrwd@gmail.com \
--cc=cebbert@redhat.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).