From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-ide@vger.kernel.org, xfs@oss.sgi.com,
Alan Piszcz <ap@solarrain.com>
Subject: Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
Date: Sat, 5 Jul 2008 19:24:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0807051923380.23222@p34.internal.lan> (raw)
In-Reply-To: <48700228.7060904@shaw.ca>
On Sat, 5 Jul 2008, Robert Hancock wrote:
> Justin Piszcz wrote:
>>> Can you post your dmesg from bootup with the controller/drive detection?
>
> So you've got 6 drives in the machine. Intel chipsets normally seem pretty
> robust with AHCI.
>
> Are you certain that your machine has enough power to run all those drives
> properly? We've seen in a number of cases that power fluctuations or noise
> can cause these kinds of errors.
I have a 650watt PSU (nice antec one) and the power draw of the box is
~148watts w/ veliciraptors, ~250 when fully load all 4 cores + all 12
disks writing. I have turned off the irqbalance daemon and I am going to
see if the problem re-occurs.
Justin.
next prev parent reply other threads:[~2008-07-05 23:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.u8J+BqAcxU1mg8ob9pMBJaAHBPo@ifi.uio.no>
2008-07-05 18:38 ` Lots of con-current I/O = resets SATA link? (2.6.25.10) Robert Hancock
2008-07-05 19:28 ` Justin Piszcz
2008-07-05 23:22 ` Robert Hancock
2008-07-05 23:24 ` Justin Piszcz [this message]
2008-07-06 10:31 ` Justin Piszcz
2008-07-06 10:44 ` Hannes Dorbath
2008-07-06 12:13 ` Justin Piszcz
2008-07-06 12:42 ` Justin Piszcz
2008-07-06 19:51 ` Justin Piszcz
2008-07-07 9:45 ` Mattias Wadenstein
2008-07-07 9:57 ` Justin Piszcz
2008-07-05 16:57 Justin Piszcz
2008-07-05 17:35 ` Jon Nelson
2008-07-05 17:35 ` Jon Nelson
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=alpine.DEB.1.10.0807051923380.23222@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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