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: Thu, 08 Oct 2009 12:42:14 -0400 [thread overview]
Message-ID: <1255020134.30440.698.camel@giskard> (raw)
In-Reply-To: <4ACC076F.7020000@rtr.ca>
El Tue, 06-10-2009 a las 23:13 -0400, Mark Lord escribió:
> Dunno. Rev.9 == "C0" in Marvell terminology,
> and that's the latest/final rev for the 6081 chip,
> with most of the PCI-X bugs fixed or worked around.
> So not much to go on there.
>
> The Bus error report was real, though.
> But with 3.0gb/sec sata connections, the chip will be
> using some different internal clocks and timings,
> which could be enough to avoid triggering the PCI errors.
>
> I guess. Let's hope so, anyway.
Our prayers have not been answered :-(
I tried several things:
- Forcing all the 500GB Seagate drives to 3.0Gbps does not help
- Replacing the 500GB drives with 1.5TB drives seems to make
the PCI error much less frequent
- Moving the controllers to different slots (on different busses)
does not help
- Happens with both 2.6.26 (from lenny) and 2.6.30 (from sid)
- Unplugging one of the controllers appeared to lead to a stable
configuration, but yesterday I left the machines reconstructing
the arrays and this mornings one of them is not answering
to pings ;-(
I want to try reducing the frequency of the PCI-X bus, but the BIOS does
not seem to provide a setting for it. Is there another way?
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
next prev parent reply other threads:[~2009-10-08 16:42 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
2009-10-07 3:13 ` Mark Lord
2009-10-08 16:42 ` Bernie Innocenti [this message]
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=1255020134.30440.698.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.