From: Tejun Heo <htejun@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH] libata: add human-readable error value decoding
Date: Thu, 10 May 2007 11:43:09 +0200 [thread overview]
Message-ID: <4642E92D.5010509@gmail.com> (raw)
In-Reply-To: <46428103.3040003@shaw.ca>
Robert Hancock wrote:
> This adds human-readable decoding of the ATA status and error registers
> (similar
> to what drivers/ide does) as well as the SATA Serror register to libata
> error
> handling output. This prevents the need to pore through standards documents
> to figure out the meaning of the bits in these registers when looking at
> error
> reports. Some bits that drivers/ide decoded are not decoded here, since
> the bits
> are either command-dependent or obsolete, and properly parsing them
> would add
> too much complexity.
>
> Signed-off-by: Robert Hancock <hancockr@shaw.ca>
>
> --- linux-2.6.21.1/drivers/ata/libata-eh.c 2007-04-27
> 15:49:26.000000000 -0600
> +++ linux-2.6.21.1edit/drivers/ata/libata-eh.c 2007-05-09
> 19:47:53.000000000 -0600
> @@ -1523,6 +1523,27 @@ static void ata_eh_report(struct ata_por
> ata_port_printk(ap, KERN_ERR, "(%s)\n", desc);
> }
>
> + if (ehc->i.serror)
> + ata_port_printk(ap, KERN_ERR,
> + "SError: {%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s}\n",
> + ehc->i.serror & SERR_DATA_RECOVERED ? "RecovDataErr " : "",
> + ehc->i.serror & SERR_COMM_RECOVERED ? "RecovCommErr " : "",
> + ehc->i.serror & SERR_DATA ? "UnrecovDataErr " : "",
> + ehc->i.serror & SERR_PERSISTENT ? "PersistErr " : "",
> + ehc->i.serror & SERR_PROTOCOL ? "ProtocolErr " : "",
> + ehc->i.serror & SERR_INTERNAL ? "HostInternalErr " : "",
> + ehc->i.serror & SERR_PHYRDY_CHG ? "PHYRdyChg " : "",
> + ehc->i.serror & SERR_PHY_INT_ERR ? "PHYInternalErr " : "",
> + ehc->i.serror & SERR_COMM_WAKE ? "CommWake " : "",
> + ehc->i.serror & SERR_10B_8B_ERR ? "10B8BErr " : "",
> + ehc->i.serror & SERR_DISPARITY ? "Disparity " : "",
> + ehc->i.serror & SERR_CRC ? "CRCErr " : "",
> + ehc->i.serror & SERR_HANDSHAKE ? "HandshakeErr " : "",
> + ehc->i.serror & SERR_LINK_SEQ_ERR ? "LinkSeqErr " : "",
> + ehc->i.serror & SERR_TRANS_ST_ERROR ? "TransStatTransErr " : "",
> + ehc->i.serror & SERR_UNRECOG_FIS ? "UnrecogFIS " : "",
> + ehc->i.serror & SERR_DEV_XCHG ? "DevExchanged " : "" );
I'm not really convinced whether this is necessary. The human readable
form is also a bit cryptic and can get quite long. So, mild NACK from me.
--
tejun
next prev parent reply other threads:[~2007-05-10 9:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 2:18 [PATCH] libata: add human-readable error value decoding Robert Hancock
2007-05-10 9:43 ` Tejun Heo [this message]
2007-05-10 13:24 ` Mark Lord
2007-05-10 16:40 ` Jeff Garzik
2007-05-10 21:33 ` Mark Lord
2007-05-10 21:42 ` Jeff Garzik
2007-05-10 23:32 ` Robert Hancock
2007-05-10 23:47 ` Jeff Garzik
2007-05-11 0:55 ` Alan Cox
2007-05-10 23:29 ` Robert Hancock
2007-05-11 16:48 ` Chuck Ebbert
2007-05-11 17:11 ` Tejun Heo
2007-05-11 23:10 ` Robert Hancock
2007-05-11 23:22 ` 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=4642E92D.5010509@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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 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.