LKML Archive on
help / color / mirror / Atom feed
From: Oskar Liljeblad <>
To: Robert Hancock <>
Subject: Re: sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard
Date: Wed, 29 Oct 2008 19:58:56 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tuesday, October 28, 2008 at 17:37, Robert Hancock wrote:
>> Hard drives (ata1/sda, ata2/sdb, ata3/sdc): Seagate ST31500341AS 1.5TB SATA
>> 19:24:26 ata2: exception Emask 0x50 SAct 0x0 SErr 0x90a02 action 0xe frozen
>> 19:24:26 ata2: irq_stat 0x00400000, PHY RDY changed
>> 19:24:26 ata2: SError: { RecovComm Persist HostInt PHYRdyChg 10B8B }
> Sounds like the drive and the controller are unhappy with each other, or  
> there's some kind of communications or hardware problem. Not likely a  
> kernel issue.
> It's unclear if limiting to 1.5 Gbps would help, you could try it and see..

It seems the solution is to disable write caching. So far no errors, and
other people confirm this solution.

Anyway Seagate (inofficially) claims it's a driver issue in Linux - from

  "We already know about the Linux issue, it is indeed a kernel error
  causing the problem as it was explained to me by one of our developers."



  reply	other threads:[~2008-10-29 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2008-10-28 23:19 ` sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard Robert Hancock
2008-10-29 18:58   ` Oskar Liljeblad [this message]
2008-10-29 20:17     ` Alan Cox
2008-10-29 20:23       ` Ric Wheeler
2008-10-29 20:52         ` Phillip O'Donnell
2008-10-29 22:37           ` Ric Wheeler
2008-11-07 11:33             ` Kasper Sandberg
2008-11-07 12:27               ` Ric Wheeler
     [not found] ` <>
     [not found]   ` <>
2008-10-30  0:39     ` [PATCH] libata: Avoid overflow in ata_tf_to_lba48() when tf->hba_lbal > 127 Robert Hancock
2008-10-28 17:01 sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard Oskar Liljeblad
2008-10-28 17:59 ` David Rees
2008-10-28 23:25 ` Phillip O'Donnell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).