From: Jon Ivar Rykkelid <jonry@pvv.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Tejun Heo <htejun@gmail.com>,
Prakash Punnoor <prakash@punnoor.de>,
linux-kernel@vger.kernel.org, Robert Hancock <hancockr@shaw.ca>
Subject: Re: sata_nv issues with MCP51 SATA controller
Date: Fri, 14 Sep 2007 20:38:30 +0200 [thread overview]
Message-ID: <46EAD526.1040601@pvv.org> (raw)
In-Reply-To: <46EAAF99.6030809@garzik.org>
Jeff Garzik wrote:
> Jon Ivar Rykkelid wrote:
>
>> I'm going to test another (identical) motherboard this evening to
>> establish whether it could be a HW-issue.
>
> Not just motherboard. It is more likely to be a cable, drive or PSU
> problem.
>> It is NOT the PSU, nor is it cables, as all the drives work well
>> using the same cables + PSU (in the same box) if I connect them to my
>> other two controllers (in that same box).
>
>
> It's sometimes the combination that matters most. You cannot really
> make that determination yet.
>
Whatever.
(Though I must confess, that in spite of my Master degree in Electrical
Engineering and extensive HW experience, I can not for the life of me
understand how you can find it more likely to be cables (that work fine
with other controllers), disks (that also work fine with other
controllers) or the power-supply (that also works fine with exactly the
same things connected to it) rather than the motherboard's
SATA-controller (that is the item that actually is reported to fail in
the first place). - Sure, I'm well aware that sometimes the combination
of HW matters, but to my experience we're normally not talking about
"dumb" stuff like cables and PSU if that is the issue.)
Anyway, I have just changed to the other (identical) motherboard, and
things are running just fine at the moment...
I'll let you know if they start acting up (as they did before). If not I
guess the fault was with the motherboard and not the driver - Guess
we'll know pretty soon...
Thanks for all your effort, gents, let's hope it all works now!
BR
Jon Ivar
next prev parent reply other threads:[~2007-09-14 18:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 7:46 sata_nv issues with MCP51 SATA controller Jon Ivar Rykkelid
2007-09-13 14:20 ` Jeff Garzik
2007-09-13 15:05 ` Jon Ivar Rykkelid
2007-09-13 15:14 ` Tejun Heo
2007-09-13 18:01 ` Jon Ivar Rykkelid
2007-09-13 19:26 ` Jon Ivar Rykkelid
2007-09-13 19:54 ` Jeff Garzik
2007-09-13 21:15 ` Jon Ivar Rykkelid
2007-09-14 0:37 ` Robert Hancock
2007-09-14 12:10 ` Jon Ivar Rykkelid
2007-09-14 13:29 ` Prakash Punnoor
2007-09-14 14:17 ` Jon Ivar Rykkelid
2007-09-14 14:25 ` Jeff Garzik
2007-09-14 14:39 ` Tejun Heo
[not found] ` <46EAAA9A.1020903@pvv.org>
2007-09-14 15:58 ` Jeff Garzik
2007-09-14 18:38 ` Jon Ivar Rykkelid [this message]
2007-09-14 20:24 ` auxsvr
2007-09-14 20:35 ` Jon Ivar Rykkelid
2007-09-15 7:12 ` Prakash Punnoor
2007-09-15 10:14 ` Jon Ivar Rykkelid
2007-09-15 14:47 ` John Stoffel
2007-09-15 19:29 ` Jon Ivar Rykkelid
[not found] ` <46EBA82C.6050000@pvv.org>
2007-09-15 11:30 ` Prakash Punnoor
-- strict thread matches above, loose matches on Subject: below --
2007-09-13 7:18 Jon Ivar Rykkelid
2007-09-13 9:16 ` Tejun Heo
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=46EAD526.1040601@pvv.org \
--to=jonry@pvv.org \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.de \
/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