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]

Date:	Tue, 2 Dec 2008 04:49:18 -0500 (EST)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
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



On Tue, 2 Dec 2008, Soeren Sonnenburg wrote:

> Dear all,
>
> 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)

A few items:

          res 40/00:00:48:19:67/00:00:1e:00:00/40 Emask 0x50 (ATA bus error)
          ata3: SError: { UnrecovData HostInt 10B8B BadCRC }

These are usually realted to a bad cable or connector.

ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Did you remove the 1.5 Gbps jumper so it can run at 3.0 Gbps?

Justin.


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