From: Tejun Heo <htejun@gmail.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-ide@vger.kernel.org, Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: Still having problems with sata_promise on all late kernels
Date: Wed, 15 Aug 2007 16:54:52 +0900 [thread overview]
Message-ID: <46C2B14C.5020004@gmail.com> (raw)
In-Reply-To: <46C1B3B5.1090303@wasp.net.au>
[cc'ing Mikael Pettersson]
Brad Campbell wrote:
> Tejun Heo wrote:
>
>> ATA bus error is a strong indicator for hardware problem. Please get a
>> separate power supply (doesn't have to be an expensive one), power it up
>> [1], and connect some of the drives to the power supply and see whether
>> errors persist on those drives.
>>
>
> 2 separate tests with the 2 troublesome drives, each time with both
> drives on a different power supply unit. Also tried new cables from a
> different manufacturer.
>
> It ain't the cables and it ain't the power.
I see. Thanks. I'm pretty much out of ideas at this point. Mikael?
--
tejun
next prev parent reply other threads:[~2007-08-15 7:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 3:04 Still having problems with sata_promise on all late kernels Brad Campbell
2007-08-14 4:37 ` Still having problems with sata_promise on all late kernels - shutdown too Brad Campbell
2007-08-14 16:42 ` Still having problems with sata_promise on all late kernels - shutdown too - BISECTED Brad Campbell
2007-08-15 7:50 ` Tejun Heo
2007-08-15 16:18 ` Brad Campbell
2007-08-16 5:43 ` Tejun Heo
2007-08-16 7:54 ` Brad Campbell
2007-08-16 11:10 ` Tejun Heo
2007-08-16 11:22 ` Brad Campbell
2007-08-14 10:20 ` Still having problems with sata_promise on all late kernels Tejun Heo
2007-08-14 10:42 ` Brad Campbell
2007-08-14 13:52 ` Brad Campbell
2007-08-15 7:54 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-15 15:39 Mikael Pettersson
2007-08-15 16:36 ` Brad Campbell
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=46C2B14C.5020004@gmail.com \
--to=htejun@gmail.com \
--cc=brad@wasp.net.au \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).