From: Tejun Heo <htejun@gmail.com>
To: Fajun Chen <fajunchen@gmail.com>
Cc: linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Libata EH False Alarm (2.6.18-rc2)?
Date: Fri, 25 Aug 2006 05:21:22 +0900 [thread overview]
Message-ID: <44EE0A42.4070104@gmail.com> (raw)
In-Reply-To: <8202f4270608241305n2e0d3e80q2bd377ae85d841bb@mail.gmail.com>
Fajun Chen wrote:
> Sil3124. That's the only chipset we use.
>> > [30540.003174] ata1: exception Emask 0x10 SAct 0x0 SErr 0x80000 action
>> > 0x2 frozen
>> > [30540.003259] ata1: (irq_stat 0x01100010, PHY RDY changed)
Yeap, this message from sata_sil24. You're not getting any phy status
changes bits in SError although the device is reporting phy rdy changed
event. However, your 3124 is reporting 8b/10b decoding error threshold
exceeded error interrupt. That could be related to the phyrdy status
changed event. This happens only under heavy IO, right? How often does
it occur in units of times per megabytes transferred?
8b/10b error is a recoverable FIS reception error. The interrupt bit
(bit 24 of irq_stat) is only turned on if threshold count is exceeded,
which is initialized to 0x8000 at the moment. This indicates that there
are quite some number of transmission failures.
--
tejun
next prev parent reply other threads:[~2006-08-24 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 19:42 Libata EH False Alarm (2.6.18-rc2)? Fajun Chen
2006-08-24 20:00 ` Tejun Heo
2006-08-24 20:05 ` Fajun Chen
2006-08-24 20:21 ` Tejun Heo [this message]
2006-08-24 20:24 ` Tejun Heo
2006-08-25 14:41 ` Fajun Chen
2006-08-25 14:54 ` Tejun Heo
2006-08-24 21:28 ` Fajun Chen
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=44EE0A42.4070104@gmail.com \
--to=htejun@gmail.com \
--cc=fajunchen@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 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).