[lkml]   [2005]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectEDAC (was: Re: 2.6.14-rc5-mm1)
Alan Cox wrote (ao):
> On Maw, 2005-10-25 at 10:55 -0700, Avuton Olrich 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
> > ... 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)?
> If the parity error is real then it would indicate a bad PCI transfer
> has occurred and data corrupted in the transfer. Unfortunately because
> some vendors don't use PCI parity checking much and some card vendors
> don't debug their products except on that OS there are some cards that
> generate spurious parity errors.
> Can you send an lspci -vxx. That'll help the EDAC folk build up a view
> of what needs to be blacklisted.

Stupid question: should EDAC work on a Via Epia board? Because I see the
"Detected Parity Error" messages too (and a lot of them), but figured
that the option is just 'not an option' :-)

If it should work I'll be happy to send the error and lspci if that

Humilis IT Services and Solutions
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-26 09:52    [W:0.088 / U:0.944 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site