linux-kernel - [SOLVED] Re: sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ cause=0x30000040

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 14 Oct 2009 11:24:25 -0400
From:	Bernie Innocenti <bernie@...ewiz.org>
To:	Tony Vroon <tony@...x.net>
Cc:	Mark Lord <liml@....ca>, Harri Olin <harri.olin@...il.com>,
	linux-ide@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	sysadmin <sysadmin@....org>
Subject: [SOLVED] Re: sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ
 cause=0x30000040

El Thu, 08-10-2009 a las 18:09 +0100, Tony Vroon escribió:
> 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.

Hurray! It seems we've fixed our stability issue at last.

We forced the bus speed down to PCI-X 66MHz for both buses by shorting
pins 1-2 of the on-board jumpers.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/