decoding MCE Logs? Possible hardware issue?

[Jerry Feldman]

On 09/29/2010 09:29 AM, Derek Atkins wrote:
> Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> writes:
>
>  =20
>>> But I suspect there's still really a hardware problem somewhere.  :(
>>>  =20
>>>
>>>      =20
>> Just one thing to add. I have a number of servers with Supermicro
>> boards, and one of them won't boot unless I blacklist one of the edac
>> modules. That system has 64GB ECC memory and either 1 or 2 Intel Xeon
>> CPUs (One of my systems only has 1 CPU the rest have 2).  If you are
>> interested I can email you with the modules I am blacklisting.
>>    =20
> Note that this is a Supermicro with AMD CPUs.  It only has 16GB RAM
> right now, but I might extend that if I find that some of the RAM is
> bad.  The system boots just fine, and I do not have any edac modules
> loaded at all (according to lsmod).  So I'm not sure what blacklisting
> it would accomplish?
>
> -derek
>
>  =20
I've got 5 systems with Supermicro X7DB8+ Mother Boards, and only one
has problems with the edac modules. In my search for a solution to the
udev hang problem I found a lot of pointers to Supermicro boards. I
don't know why that one has the issue. It certainly is a much different
issue than you have. My lsmod on another system shows:
[gaf at boslc05 ~]$ lsmod | grep edac
i5000_edac             42177  0
edac_mc                60193  1 i5000_edac

In any case I was just trying to provide some additional information.

--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846