[lkml]   [2005]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.14-rc5-mm1
    On 10/24/05, Andrew Morton <> wrote:

    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)?


    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
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-10-25 19:58    [W:0.027 / U:32.692 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site