linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Effenberger <florian@effenberger.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: libata interface fatal error
Date: Mon, 18 Jun 2007 13:28:49 +0200	[thread overview]
Message-ID: <46766C71.6030607@effenberger.org> (raw)
In-Reply-To: <467664F6.4060607@gmail.com>

Hi Tejun,

> Hmmm... Can you use a separate PSU to power two of the four drives and
> see what happens?  Just power up a PSU as directed in the following
> webpage and connect two of the harddrives to the PSU.
> 
>   http://modtown.co.uk/mt/article2.php?id=psumod

thanks for that link, we will try that and keep you updated what happens!

> I don't know.  Till now all the problem cases have been isolated to a
> specific controller / drive combination (sata_promise and newer seagate
> drives) or hardware configuration problem (most of them being PSU
> issues), so I don't think we need such option yet.  If you have a
> problematic hardware which pukes on 3.0Gbps, libata should do the right
> thing after complaining a bit which IMHO isn't too bad.

So, loss of data or data corruption can't occur, even when we have to 
wait until the speed is limited?

Florian














  reply	other threads:[~2007-06-18 11:28 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26  9:43 libata interface fatal error Florian Effenberger
2007-05-29  9:16 ` Tejun Heo
2007-05-29 14:16   ` Florian Effenberger
2007-06-06 21:23   ` Florian Effenberger
2007-06-07  9:50     ` Tejun Heo
2007-06-07 14:08       ` Florian Effenberger
2007-06-13 10:37       ` Florian Effenberger
2007-06-14  9:43         ` Tejun Heo
2007-06-14 11:12           ` Florian Effenberger
2007-06-14 12:25             ` Tejun Heo
2007-06-14 15:12               ` Florian Effenberger
2007-06-18  3:10                 ` Tejun Heo
2007-06-18  6:08                   ` Tomi Orava
2007-06-18  6:28                     ` Tejun Heo
2007-06-18 10:38                   ` Florian Effenberger
2007-06-18 10:44                     ` Tejun Heo
2007-06-16 10:23       ` Florian Effenberger
2007-06-18  3:13         ` Tejun Heo
2007-06-18 10:44           ` Florian Effenberger
2007-06-18 10:56             ` Tejun Heo
2007-06-18 11:28               ` Florian Effenberger [this message]
2007-06-18 11:30                 ` Tejun Heo
2007-06-18 11:32                   ` Florian Effenberger
2007-06-24 11:32               ` Florian Effenberger
2007-06-25  2:49                 ` Tejun Heo
2007-06-25  8:47                   ` Florian Effenberger
  -- strict thread matches above, loose matches on Subject: below --
2007-06-18  7:05 Mikael Pettersson
2007-06-18  7:13 ` Tejun Heo
2007-06-18 10:47   ` Florian Effenberger
2007-06-18 17:14 ` Ansgar Knappheide
2007-06-18 18:54 ` Tomi Orava
2007-05-24 13:25 Florian Effenberger
2007-05-24 13:45 ` Tejun Heo
2007-05-24 14:08   ` Florian Effenberger
2007-05-24 14:21     ` Tejun Heo
2007-05-24 14:47       ` Florian Effenberger
2007-05-24 14:53         ` Tejun Heo
2007-05-24 15:28           ` Florian Effenberger
2007-05-24 14:55         ` Greg Freemyer
2007-05-24 14:59           ` Tejun Heo
2007-05-24 15:00           ` Florian Effenberger

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=46766C71.6030607@effenberger.org \
    --to=florian@effenberger.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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).