From: "Espen Fjellvær Olsen" <espen@oxygen.tihlde.org>
To: linux-kernel@vger.kernel.org
Cc: "Drift@tihlde" <drift@tihlde.org>
Subject: Machine Check Exception on Opteron 265
Date: Sat, 14 Apr 2007 16:58:43 +0200 [thread overview]
Message-ID: <4620EC23.4010404@mrfjo.org> (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
espen@mrfjo.org
next reply other threads:[~2007-04-14 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 14:58 Espen Fjellvær Olsen [this message]
2007-04-17 13:56 ` Machine Check Exception on Opteron 265 Alan Cox
2007-04-17 13:57 ` Matthew Garrett
2007-04-17 14:18 ` Espen Fjellvær Olsen
[not found] <fa.bATEBhtZlyN0K1NKutzIYJJSRC0@ifi.uio.no>
2007-04-14 15:39 ` Robert Hancock
2007-04-16 6:31 ` Joachim Deguara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4620EC23.4010404@mrfjo.org \
--to=espen@oxygen.tihlde.org \
--cc=drift@tihlde.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.