From: Tejun Heo <htejun@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: [RFT] sata_promise: decode and report error reasons
Date: Thu, 08 Mar 2007 11:44:27 +0900 [thread overview]
Message-ID: <45EF788B.3080300@gmail.com> (raw)
In-Reply-To: <17903.6217.992304.800959@alkaid.it.uu.se>
Hello,
Jeff clarified most things. Just few more things.
Mikael Pettersson wrote:
> Which SErrror bits are standard?
> It is true that some of the SError bits are diagnostic rather than
> actual error indicators, as Promise's driver only checks a subset
> of them. I'll fix that.
Pretty much most of them. Just take a look at SError section in
serialATA spec. libata EH decodes most of error and some of diagnostic
bits in ata_eh_analyze_serror().
> ATA_DMA_CNT_ERR is when a DMA FIS data size differs from total DMA S/G size.
> I think AC_ERR_ATA_BUS is the correct choice for this one too.
AC_ERR_ATA_BUS is a bit special in that if it happens repeatedly it will
trigger transfer speed adjustment pretty quickly. The error should be
set iff the error is a transmission error on the wire which is likely to
be fixed by slowing down the transfer rate. Maybe it should have been
named AC_ERR_ATA_TRANSMISSION or something.
As Jeff pointed out, AC_ERR_HSM is usually used when we can receive the
FIS correctly but it doesn't make sense. This is usually caused by
driver error or seriously brain damaged firmware. :-)
Thanks.
--
tejun
prev parent reply other threads:[~2007-03-08 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 1:58 [RFT] sata_promise: decode and report error reasons Mikael Pettersson
2007-03-05 4:35 ` Tejun Heo
2007-03-07 19:53 ` Mikael Pettersson
2007-03-07 22:45 ` Jeff Garzik
2007-03-08 10:09 ` Mikael Pettersson
2007-03-08 2:44 ` 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=45EF788B.3080300@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).