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: Thu, 14 Jun 2007 17:12:27 +0200 [thread overview]
Message-ID: <46715ADB.4020202@effenberger.org> (raw)
In-Reply-To: <467133D7.7070000@gmail.com>
Hi Tejun,
> Okay, ich8. I don't think the chipset is at fault here and you have a
> lot of disks. My primary suspect is power supply problem but things
> like this are hard to prove. With the merged speed down fix, libata
> will do the right thing after a few errors, so ignoring the problem
> wouldn't be a too bad idea. If you're curious, you can try to connect
> drives to different SATA ports and power lanes and see whether errors
> follow the disk, port or power lane.
exactly, should be four disks in the machine.
What power supply would you recommend for this type of disks? I think we
got a 450W Enermax, IIRC.
What do you mean by "merged speed down fix"? Is your fix for the speed
down logic implemented in the current kernel, so I don't have to patch
anymore (except when I want to force 1.5Gbps right from the beginning)?
All SATA parts are used, so reconnecting is not an option. But I can try
to switch the power supply (lanes).
Thanks for all your kind help, that is much appreciated!
Florian
next prev parent reply other threads:[~2007-06-14 15:12 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 [this message]
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
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=46715ADB.4020202@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 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.