CentOS - Jan 2008 - EDAC error

Hello,

I upgraded to CentOS 5.1 and everything went smoothly (Thanks for the  
awesome work!). But after rebooting, I get the following error:

EDAC MC: Ver: 2.0.1 Nov 30 2007
EDAC e7xxx: error reporting device not found:vendor 8086 device  
0x2541 (broken BIOS?)

I found http://edacbugs.buttersideup.com/show_bug.cgi?id=21 with  
google but no solution. Is it safe to ignore the error or remove the  
EDAC module? I read their wiki but I'm new to this and I don't want  
to break anything?

Please advice on what to do next?

Thank you so much.

dianne 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20080119/f4d76ccb/attachment-0002.html>

On Saturday 19 January 2008, Dianne Yumul wrote:
> Hello,
>
> I upgraded to CentOS 5.1 and everything went smoothly (Thanks for the
> awesome work!). But after rebooting, I get the following error:
>
> EDAC MC: Ver: 2.0.1 Nov 30 2007
> EDAC e7xxx: error reporting device not found:vendor 8086 device
> 0x2541 (broken BIOS?)
>
> I found http://edacbugs.buttersideup.com/show_bug.cgi?id=21 with
> google but no solution. Is it safe to ignore the error or remove the
> EDAC module? I read their wiki but I'm new to this and I don't want
> to break anything?
It's safe to not load EDAC at all, but also safe to leave it loaded and
ignore
the error (I'd actually call it a warning). If the functionality is very 
important to your then you might want to do as EDAC suggests and investigate 
BIOS upgrades (or just have a look at the relevant BIOS settings).

/Peter
> Please advice on what to do next?
>
> Thank you so much.
>
> dianne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL:
<http://lists.centos.org/pipermail/centos/attachments/20080128/7fdcaa3e/attachment-0002.sig>

On Jan 28, 2008, at 2:46 AM, Peter Kjellstrom wrote:
> It's safe to not load EDAC at all, but also safe to leave it loaded  
> and ignore
> the error (I'd actually call it a warning). If the functionality is  
> very
> important to your then you might want to do as EDAC suggests and  
> investigate
> BIOS upgrades (or just have a look at the relevant BIOS settings).
>
> /Peter
I think I will do as you suggest and just ignore it for now. Thank  
you very much.

Dianne