strange eth behavior

[vu Pham]

On 12/18/2012 9:45 AM, Lonni J Friedman wrote:
> On Tue, Dec 18, 2012 at 7:35 AM, vu Pham <vu at sivell.com> wrote:
>>
>> On 12/18/2012 9:28 AM, Lonni J Friedman wrote:
>>> On Tue, Dec 18, 2012 at 7:24 AM, vu Pham <vu at sivell.com> wrote:
>>>> By the way, the MB is replaced because of the CPU check error, not the
>>>> eth problem :)
>>>>
>>>
>>> By CPU check error, you mean a machine check exception, or something
>>> else?  Unless this is some very strange abomination of a mobo, a CPU
>>> MCE typically means that you replace the CPU, not the entire mobo.
>>> Granted, Dell might have some non-standard motherboard where the CPU
>>> is not a field replaceable unit, and requires the entire mobo to get
>>> swapped out.
>>
>> The exact error is "cpu 1 machine check error detected". I think it is
>> an MCE.  The problem started last week with the same error and I
>> upgraded all the firmwares. It happened again last night when I got the
>> strange eth behavior.
>>
>
> Yes, that's a machine check exception.  its quite possible that the
> flaky CPU was what was causing the NIC to misbehave.  I've also seen
> cases where a MCE is triggered by a flaw in the mobo, rather than the
> CPU.  It all depends on the content of the MCE message (its not a
> generic error).
>

They came and replaced both the MB and CPU. Perhaps they do not want to 
take a chance.

Vu