From: Tony Vroon <tony@linx.net>
To: Bernie Innocenti <bernie@codewiz.org>
Cc: Mark Lord <liml@rtr.ca>, 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 18:09:47 +0100 [thread overview]
Message-ID: <1255021787.3386.24.camel@localhost> (raw)
In-Reply-To: <1255020134.30440.698.camel@giskard>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Thu, 2009-10-08 at 12:42 -0400, Bernie Innocenti wrote:
> El Tue, 06-10-2009 a las 23:13 -0400, Mark Lord escribió:
> 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?
Generally this is done with a physical jumper on the board instead.
You'll find it near to the bridge chip, which is almost always by NEC.
Another technique to slow the bridge down is to insert a regular PCI
card in the other slot (these bridges tend to offer 2 or 3 slots). As
the weakest link, it'll drag everything down to 33MHz.
An old PCI-X 66MHz-only card may prove helpful here as well. You don't
have to drive it in any way; getting power to it is sufficient.
Regards,
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-08 17:11 UTC|newest]
Thread overview: 16+ 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
2009-10-08 17:09 ` Tony Vroon [this message]
2009-10-14 15:24 ` [SOLVED] " Bernie Innocenti
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=1255021787.3386.24.camel@localhost \
--to=tony@linx.net \
--cc=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).