From: Jon Ivar Rykkelid <jonry@pvv.org>
To: linux-kernel@vger.kernel.org
Cc: John Stoffel <john@stoffel.org>,
Prakash Punnoor <prakash@punnoor.de>,
Robert Hancock <hancockr@shaw.ca>, Tejun Heo <htejun@gmail.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: sata_nv issues with MCP51 SATA controller
Date: Sat, 15 Sep 2007 21:29:59 +0200 [thread overview]
Message-ID: <46EC32B7.7010404@pvv.org> (raw)
In-Reply-To: <18155.61586.118828.112512@stoffel.org>
John Stoffel wrote:
> What happens when you just have ONE disk connected to the motherboard
> controller, and the rest connected to PCI controllers? Does it crap
> out then? You've just such a nice repeatable problem across
> motherboards that it's a shame to waste this debugging time.
>
Sorry, I gave in. I have now abandoned my nvidia trials (both
motherboards have been returned, and I'm now running with Intel chipset)
- My current motherboard is less ideal (in terms of PCI-slots etc.), but
on the other hand it works...
> I'm wondering if it's a PCI bus issue somehow, and that the load on
> the motherboard controller isn't supportable when you have a bunch of
> disks on PCI controllers as well. Shot in the dark...
>
That was actually not such a bad idea... Unfortunately it's too late now
(If not I should have tested for sure). I was/am after all running an
8-disk SATA array (plus a normal IDE disk - not in the raid). I had 4
disks running through two PCI-cards and 4 disks used the motherboard's
controller. - When all 8 disks were connected to the two PCI-cards the
speed dropped compared to when the motherboard's controller took some
load.. (So it could maybe be an issue with bandwidth / load ? - I don't
know.)
> Thanks for all your hard work on this, I know how frustrating it is to
> not have a stable system!
>
Sorry for giving in, but I felt I was banging my head against the wall
(and with too few sensible solutions being suggested). Now I guess I'm
semi-happy that all seems to work OK with the Intel chipset..
Frustrating that the sata_nv-driver / nvidia HW didn't work with my
configuration, though...
Thank you all for your effort as well - hope someone figures this out
sometime in the future.
All the best
Jon Ivar
next prev parent reply other threads:[~2007-09-15 19:30 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
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 [this message]
[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=46EC32B7.7010404@pvv.org \
--to=jonry@pvv.org \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=john@stoffel.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