Skip to contentSkip to conversation

Machine Check Exception on Opteron 265

DISCUSSION Espen Fjellvær Olsen 4 participants 4 messages Apr 14, 2007 – Apr 17, 2007

lore
Share & tools
lore
#0 lore raw

Hi!
Today our Opteron 265, 2x2, paniced after many months uptime, giving only this error message:

HARDWARE ERROR
CPU 2: Machine Check Exception: 4 Bank 4: b60a200100000813
TSC 6bb9fd0142921a ADDR a891e9b8
This is not a software problem!

mcelog --ascii gives this on the above error:

HARDWARE ERROR
CPU 2 4 northbridge TSC 6bb9fd0142921a
Northbridge ECC error
ECC syndrome = 14
bit32 = err cpu0
bit45 = uncorrected ecc error
bit57 = processor context corrupt
bit61 = error uncorrected
bus error 'local node origin, request didn't time out
generic read mem transaction
memory access, level generic'
STATUS b60a200100000813 MCGSTATUS 4
This is not a software problem!

As far as we know there wasnt any unuasal activity on the server at the time.
We updated glibc yesterday, but that shouldnt really cause such a problem. So now we wonder if this might be an MCE bug, or really a HW problem, and if it is one of the CPUs, or the RAM thats faulty.
We are running 2.6.18.

--
Mvh
Espen Fjellvær Olsen
Drift@Tihlde
[email protected]

#1 lore raw
Quoted 8 lines · On Sat, 14 Apr 2007 16:58:43 +0200 Espen Fjellvær Olsen…

Hi!
Today our Opteron 265, 2x2, paniced after many months uptime, giving only this error message:

HARDWARE ERROR
CPU 2: Machine Check Exception: 4 Bank 4: b60a200100000813
TSC 6bb9fd0142921a ADDR a891e9b8
This is not a software problem!

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^]

This is there for a good reason.

Quoted 3 lines

We updated glibc yesterday, but that shouldnt really cause such a problem. So now we wonder if this might be an MCE bug, or really a HW problem, and if it is one of the CPUs, or the RAM thats faulty.

Consult your hardware vendor but if its a single event in a year it might be anything - even cosmic rays.

Alan

#2 lore raw
Quoted 6 lines · Alan Cox
Quoted 4 lines · On Sat, 14 Apr 2007 16:58:43 +0200 Espen Fjellvær Olsen…

Hi!
Today our Opteron 265, 2x2, paniced after many months uptime, giving only this error message:

Quoted 7 lines
Quoted 4 lines

HARDWARE ERROR
CPU 2: Machine Check Exception: 4 Bank 4: b60a200100000813
TSC 6bb9fd0142921a ADDR a891e9b8
This is not a software problem!

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^]

This is there for a good reason.

Though we saw MCEs being generated by running the HPA code on sata_nv with awdma, so it's not always true. I agree that in this case, it probably is.

Signature · 1 line
Matthew Garrett | [email protected]
#3 lore raw
In reply to Alan Cox
Quoted 8 lines · Alan Cox
Quoted 4 lines · On Sat, 14 Apr 2007 16:58:43 +0200 Espen Fjellvær Olsen…

Hi!
Today our Opteron 265, 2x2, paniced after many months uptime, giving only this error message:

Quoted 5 lines
Quoted 5 lines

HARDWARE ERROR
CPU 2: Machine Check Exception: 4 Bank 4: b60a200100000813
TSC 6bb9fd0142921a ADDR a891e9b8
This is not a software problem!

*snip*

Quoted 3 lines

Consult your hardware vendor but if its a single event in a year it might be anything - even cosmic rays.

Yeah, we have had more crashes now, and have removed some of our DIMMs in hope of getting a stable system again.
And ofcourse running memtest on those DIMMs. Hope it is one of those, and not one the CPUs =)

Signature · 4 lines
Mvh
Espen Fjellvær Olsen
Drift @ Tihlde
[email protected]