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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4935F63C.9080207@kernel.org>
Date:	Wed, 03 Dec 2008 12:00:12 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Soeren Sonnenburg <kernel@....de>
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

hello,

Soeren Sonnenburg wrote:
> I just purchased a seagate 1.5TB drive ST31500341AS, with firmware
> revision CC1G (which according to seagate is not affected by the cache
> flush bug) and I am getting the errors below (after almost a day of
> uptime without problems). The drive is replacing a 750G variant from
> seagate with which I had months of uptime and no errors whatsoever.
> 
> I hope anyone has an idea?
> 
> - relevant part of hdparm -I and lspci
> 
> ATA device, with non-removable media
> 	Model Number:       ST31500341AS                            
> 	Firmware Revision:  CC1G    
> 	Transport:          Serial
> 
> 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA
> AHCI Controller
> 
> - 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)...

1. inadequate power supply

2. device and controller don't like each other on 3Gbps

3. cable too long or flaky connector (especially w/ eSATA cables or
   genders or backplanes)

4. faulty controller or drive

-- 
tejun
--
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/