From: Tejun Heo <tj@kernel.org>
To: Soeren Sonnenburg <kernel@nn7.de>
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: Wed, 03 Dec 2008 12:00:12 +0900 [thread overview]
Message-ID: <4935F63C.9080207@kernel.org> (raw)
In-Reply-To: <1228205289.29251.32.camel@localhost>
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
next prev parent reply other threads:[~2008-12-03 3:00 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 [this message]
2008-12-04 7:48 ` Soeren Sonnenburg
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=4935F63C.9080207@kernel.org \
--to=tj@kernel.org \
--cc=kernel@nn7.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).