From: Tejun Heo <htejun@gmail.com>
To: Florian Effenberger <florian@effenberger.org>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: libata interface fatal error
Date: Mon, 18 Jun 2007 19:56:54 +0900 [thread overview]
Message-ID: <467664F6.4060607@gmail.com> (raw)
In-Reply-To: <46766208.1080305@effenberger.org>
Florian Effenberger wrote:
> Hi,
>
>> The controller being ich8, I'm pretty sure it isn't a driver problem.
>
> I think so, too. The Intel chipsets have shown to be very good in the past.
>
>> Do the errors occur on all four drives? Also, if things work after
>> speed is downgraded to 1.5Gbps, it doesn't really matter. There's no
>> noticeable performance difference for single disk anyway.
>
> Yes, they do occur on all drives, as far as I know. With 1.5Gbps, the
> error doesn't occur much as often and not under normal circumstances,
> only when doing a real hard stress test.
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
> Would it make sense to downgrade to 1.5 Gbps via a boot option?
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.
--
tejun
next prev parent reply other threads:[~2007-06-18 10:57 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 [this message]
2007-06-18 11:28 ` Florian Effenberger
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=467664F6.4060607@gmail.com \
--to=htejun@gmail.com \
--cc=florian@effenberger.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.