Messages in this thread | | | Date | Tue, 25 Oct 2005 10:55:52 -0700 | From | Avuton Olrich <> | Subject | Re: 2.6.14-rc5-mm1 |
| |
On 10/24/05, Andrew Morton <akpm@osdl.org> wrote: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
After upgrading to 2.6.14-rc5-mm1 I have been greeted with:
PCI-Bridge- Detected Parity Error on 0000:00:08.0 0000:00:08.0
Which is:
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 00009000-0000afff Memory behind bridge: e2000000-e5ffffff Prefetchable memory behind bridge: e6000000-e6ffffff BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
... I probably get a new one every minute or so. Is this new, perhaps part of the new EDAC stuff? And what kind of adverse effect does this have on my computer (the actual parity error)?
Thanks, avuton
-- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |