Bad memory module?

Soham Chakraborty sohamwonderpiku4u at
Thu Nov 24 00:43:31 UTC 2011

On Thu, Nov 24, 2011 at 3:10 AM, Dean S. Messing <deanm at>wrote:

> On Thu, 24 Nov 2011, Soham Chakraborty wrote.
> > On Thu, Nov 24, 2011 at 2:11 AM, Dean S. Messing wrote:
> > > Do you know what this message actually means?
> > >
> >
> > It basically means memory error checking on a memory module along with a
> > parity checking bit. It is calculated when one byte of memory is written
> > and then again when it is read. If the parity has changed, then the
> memory
> > has been changed.
> >
> > Since you have a correctable error, it shouldn't be any problem with the
> > memory module.
> Thanks!  But now I'm curious: Is the edac module running an entire
> memory check each time it writes this error out?  If not, how is it
> detecting this?  Is the kernel simply doing this parity check on each
> r/w?
> Also, if it's not a problem with the memory module, what might it be a
> problem with?  This just started happening night before last.  The error
> messages don't appear in any previous "messages" files.
I am really not sure about how internally it works. If no one answers, I
will try to gather some information. Also, can you do a lsmod and grep with

> > Also, you can blacklist the edac module, afaik and let the
> > BIOS do the error detection and correction.
> Good to know. Thanks.  But I'd like to trace and fix whatever is causing
> the problem, if indeed there is one.

> Dean
> --
> users mailing list
> users at
> To unsubscribe or change subscription options:
> Guidelines:

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the users mailing list