From: Mark Lord <liml@rtr.ca>
To: Jim Paris <jim@jtan.com>
Cc: Denys Dmytriyenko <denis@denix.org>, linux-ide@vger.kernel.org
Subject: Re: sata_sil24 stability and performance
Date: Tue, 19 Feb 2008 10:32:07 -0500 [thread overview]
Message-ID: <47BAF677.5000602@rtr.ca> (raw)
In-Reply-To: <20080219043659.GA11936@jim.sh>
Jim Paris wrote:
> ..
> As you may have noticed on this list, power supplies are very
> frequently a problem.
..
Actually, no, I haven't noticed that. :)
I do see them more frequently being suggested as a possible problem,
and then after some time and expense on the part of the reporters
it nearly always turns out to have been a device driver bug,
or (less often) a firmware quirk of the device.
Yes, PSUs are often suggested as a problem here,
but only rarely has that been true.
Especially nowadays, as PSUs are becoming much larger than
they historically once were.
Cheers
(been around here since 1993 or so)
next prev parent reply other threads:[~2008-02-19 15:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 2:09 sata_sil24 stability and performance Denys Dmytriyenko
2008-02-19 4:36 ` Jim Paris
2008-02-19 6:39 ` Denys Dmytriyenko
2008-02-19 15:32 ` Mark Lord [this message]
2008-03-02 6:14 ` Denys Dmytriyenko
2008-03-02 9:39 ` Gabor FUNK
2008-03-04 0:02 ` Tejun Heo
2008-03-04 0:22 ` Denys Dmytriyenko
2008-03-04 3:28 ` Tejun Heo
2008-03-04 6:29 ` Denys Dmytriyenko
2008-03-05 8:11 ` Tejun Heo
2008-03-06 4:14 ` Denys Dmytriyenko
2008-03-06 4:25 ` Tejun Heo
2008-03-06 6:55 ` Denys Dmytriyenko
2008-03-06 7:08 ` Tejun Heo
2008-03-15 21:43 ` Denys Dmytriyenko
2008-03-17 3:09 ` Mark Lord
2008-03-18 0:15 ` Denys Dmytriyenko
2008-03-18 4:09 ` Tejun Heo
2008-03-18 4:53 ` Denys Dmytriyenko
2008-03-18 6:40 ` Tejun Heo
2008-03-20 22:37 ` Denys Dmytriyenko
2008-03-21 0:18 ` Tejun Heo
2008-04-14 1:19 ` Denys Dmytriyenko
2008-04-14 2:49 ` Tejun Heo
2008-04-14 10:55 ` Gabor FUNK
2008-03-18 9:14 ` Gabor FUNK
2008-03-18 13:06 ` Gabor FUNK
2008-03-18 20:05 ` Mark Lord
2008-03-18 20:06 ` Mark Lord
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=47BAF677.5000602@rtr.ca \
--to=liml@rtr.ca \
--cc=denis@denix.org \
--cc=jim@jtan.com \
--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).