From: Tejun Heo <htejun@gmail.com>
To: thomas.schorpp@gmail.com
Cc: thomas schorpp <thomas.schorpp@googlemail.com>,
Mikael Pettersson <mikpe@it.uu.se>,
Robert Hancock <hancockrwd@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: HSM violations from ATA PACKET cmd ABRT errors in initial comms with LG GH22 SATA DVDRW
Date: Wed, 20 Jan 2010 17:51:49 +0900 [thread overview]
Message-ID: <4B56C425.2030203@gmail.com> (raw)
In-Reply-To: <4B56B76E.9030304@gmail.com>
Hello,
On 01/20/2010 04:57 PM, thomas schorpp wrote:
>> I think AC_ERR_OTHER can still be too much. AC_ERR_* bits should only
>> be set when the command failed for that reason. Here, underrun is
>
> Overruns from my port status log, not underruns?
> port_status 0x20280000, 0x2020, (Data Transfer Overrun Error & Target
> Device Fault)?
Well, it depends on which way you look from. It's data underrun from
the device and overrun from the sglist. Apparently sata_promise likes
to see it from the sglist. :-)
>> expected, so not really an error condition. But, for example, under
>> or overrun for an ATA R/W command should trigger HSM failure. I think
>> the above error detection logic needs to be improved a bit.
>
> Well I generally don't feel comfortable with any unknown state output
> EHs, too, but if ata spec conformant, we're fine, aren't we?
Yeap, I was just saying that the condition here wasn't really an error
condition and as such shouldn't set AC_ERR_* bit.
Thanks.
--
tejun
prev parent reply other threads:[~2010-01-20 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 20:37 HSM violations from ATA PACKET cmd ABRT errors in initial comms with LG GH22 SATA DVDRW thomas schorpp
2009-12-27 21:43 ` Robert Hancock
2009-12-28 23:44 ` Mikael Pettersson
2009-12-29 9:06 ` thomas schorpp
2009-12-30 22:40 ` thomas schorpp
2009-12-31 11:55 ` thomas schorpp
2010-01-03 21:36 ` Mikael Pettersson
2010-01-04 2:00 ` thomas schorpp
2010-01-04 9:22 ` Mikael Pettersson
2010-01-04 21:06 ` thomas schorpp
2010-01-20 3:00 ` Tejun Heo
2010-01-20 7:57 ` thomas schorpp
2010-01-20 8:51 ` 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=4B56C425.2030203@gmail.com \
--to=htejun@gmail.com \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=thomas.schorpp@gmail.com \
--cc=thomas.schorpp@googlemail.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).