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

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

Well then perhaps they would care to share the information with us 8)

The HPA size reporting one is certinly Linux, the flush cache one I don't
think is. The fact Mac people report it and Seagate suggest workarounds
of the form of "don't use 33% of the disk" don't inspire confidence.

>   "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."

Well if they'd care to explain it to linux-ide perhaps we can find a work
around. I would be cautious about disabling the write caching as it will
harm both performance and probably drive lifetime.


  reply	other threads:[~2008-10-29 20:17 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
2008-10-29 20:17     ` Alan Cox [this message]
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).