From: Tejun Heo <htejun@gmail.com>
To: philippe.grenard@m4x.org
Cc: Andrew Morton <akpm@osdl.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: (Another?) Seagate / Sil3112a problem...
Date: Mon, 08 Jan 2007 12:52:32 +0900 [thread overview]
Message-ID: <45A1C000.7080500@gmail.com> (raw)
In-Reply-To: <200701071704.36288.philippe.grenard@m4x.org>
Hello,
[cc'ing lkml and linux-ide]
Philippe Grenard wrote:
> To "close" this problem, here are the latest news :
> I just bought some new power supply, and the problem has gone...
> Maybe that was due to poor power flow or crappy connexion ?...
>
> now everything seems to work well, so as suspected, it was probably hardware
> problem.
>
> Sorry for that "false alarm", thanks again for everything, and keep up the
> good work!
Ah... so it was another one of those PSU problems. This problem is
becoming more prevalent these days. Dual 12v lane PSUs suck for driving
a lot of disks. They don't seem to allocate enough power to molex/sata
connectors.
--
tejun
parent reply other threads:[~2007-01-08 3:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200701071704.36288.philippe.grenard@m4x.org>]
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=45A1C000.7080500@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.grenard@m4x.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).