From: Soeren Sonnenburg <kernel@nn7.de>
To: Tejun Heo <tj@kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: ST31500341AS vs ICH10, exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen
Date: Thu, 04 Dec 2008 08:48:39 +0100 [thread overview]
Message-ID: <1228376919.3927.72.camel@localhost> (raw)
In-Reply-To: <4935F63C.9080207@kernel.org>
On Wed, 2008-12-03 at 12:00 +0900, Tejun Heo wrote:
> hello,
Hi Tejun, Hi list,
[...]
> > - the error(tm)
> >
> > ata3.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen
> > ata3.00: irq_stat 0x08000000, interface fatal error
> > ata3: SError: { UnrecovData HostInt 10B8B BadCRC }
>
> Your machine seems to be suffering genuine link layer problem. In
> most cases, this indicates hardware problem and in my experience
> common causes are (in the order of ballpark frequency)...
First of all thanks for your reply! Would be nice to have an FAQ with
all the errors and the most common causes somewhere...
> 1. inadequate power supply
this I would exclude (as I cannot trigger the problem by increasing load
while writing to the 4 disks in the machine)
> 2. device and controller don't like each other on 3Gbps
possible
> 3. cable too long or flaky connector (especially w/ eSATA cables or
> genders or backplanes)
might have been the problem in this case.
> 4. faulty controller or drive
the controller should be OK as it was working with another drive.
But as the problem only appeared once and I did all kinds of tests in
the last two days without this problem to re-appear I guess it must have
been either:
a) hot plug attempt with first only having a 1.5Gps drive in the
backplane
b) the connection was somehow flaky between drive and backplane (drive
was not inserted properly - still strange that it took >8 hrs to trigger
the problem).
I will keep an eye on it, but I don't expect the problem to re-appear -
but having had bad experiences with all kinds of controller/disk setups
and reading about the seagate firmware bug in earlier firmware revisions
of this drive made me alert..
So sorry for the noise and thanks for the helpful response!
Soeren
prev parent reply other threads:[~2008-12-04 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 8:08 ST31500341AS vs ICH10, exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen Soeren Sonnenburg
2008-12-02 9:49 ` Justin Piszcz
2008-12-02 14:05 ` Soeren Sonnenburg
2008-12-03 3:00 ` Tejun Heo
2008-12-04 7:48 ` Soeren Sonnenburg [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=1228376919.3927.72.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).