On Thu, Nov 24, 2011 at 3:10 AM, Dean S. Messing <deanm@xxxxxxxxxxxxx> wrote:
On Thu, 24 Nov 2011, Soham Chakraborty wrote.Thanks! But now I'm curious: Is the edac module running an entire
> 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.
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 edac.
Good to know. Thanks. But I'd like to trace and fix whatever is causing
> Also, you can blacklist the edac module, afaik and let the
> BIOS do the error detection and correction.
the problem, if indeed there is one.
Dean
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Thanks,
Soham
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
