From: Bernie Innocenti <bernie@codewiz.org>
To: Mark Lord <liml@rtr.ca>
Cc: Harri Olin <harri.olin@gmail.com>,
linux-ide@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
sysadmin <sysadmin@gnu.org>
Subject: Re: sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ cause=0x30000040
Date: Tue, 06 Oct 2009 21:40:18 -0400 [thread overview]
Message-ID: <1254879618.1471.525.camel@giskard> (raw)
In-Reply-To: <1254873978.1471.463.camel@giskard>
El Tue, 06-10-2009 a las 20:06 -0400, Bernie Innocenti escribió:
> > The early revs of these chips did have a number of errata specific to PCI-X.
>
> I checked the revision (09) against the sata_mv source and I couldn't
> spot anything relevant to us.
NEWSFLASH: today we replaced the 4x500GB Seagate drives with 4x1.5TB
drives and reconstruction of the array has been running for 2h without a
glitch.
One interesting difference is that the 500GB drives were being
configured in 1.5Gbps SATA mode. Another notable difference is the
sequential read speed: ~70MB/s vs ~130MB/s with the 1.5TB model.
Could the PCI bus errors be a red herring?
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
next prev parent reply other threads:[~2009-10-07 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 5:10 sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ cause=0x30000040 Bernie Innocenti
2009-10-05 21:45 ` Mark Lord
2009-10-06 4:16 ` Bernie Innocenti
2009-10-06 12:25 ` Harri Olin
2009-10-06 18:04 ` Bernie Innocenti
2009-10-06 20:06 ` Mark Lord
2009-10-07 0:06 ` Bernie Innocenti
2009-10-07 1:40 ` Bernie Innocenti [this message]
2009-10-07 3:13 ` Mark Lord
2009-10-08 16:42 ` Bernie Innocenti
2009-10-08 17:09 ` Tony Vroon
2009-10-14 15:24 ` [SOLVED] " Bernie Innocenti
2009-10-09 2:22 ` Christian Pernegger
2009-10-09 3:07 ` Mark Lord
2009-10-09 3:16 ` Mark Lord
2009-10-08 16:26 ` Bernie Innocenti
2009-10-08 21:51 ` Harri Olin
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=1254879618.1471.525.camel@giskard \
--to=bernie@codewiz.org \
--cc=harri.olin@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sysadmin@gnu.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).