linux-kernel - Re: ST31500341AS vs ICH10, exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1228376919.3927.72.camel@localhost>
Date:	Thu, 04 Dec 2008 08:48:39 +0100
From:	Soeren Sonnenburg <kernel@....de>
To:	Tejun Heo <tj@...nel.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linux-ide <linux-ide@...r.kernel.org>
Subject: Re: ST31500341AS vs ICH10, exception Emask 0x50 SAct 0x1 SErr
	0x280900 action 0x6 frozen

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/