From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: MCE Errors, Bad CPU, Memory or Motherboard?
Date: Fri, 10 Mar 2006 06:44:46 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603100642220.1165@p34> (raw)
This is the first time I have seen an MCE error, googling the EIP value at
the time of the panic does not return any useful results.
Does anyone know whether it is the CPU or MEMORY that is bad in this
machine? As it shows some problems with BANK4; however, if the CPU is
bad, then it is possible to get all sorts of unpredictable results, right?
Dec 9 23:21:25 box CPU 0: Machine Check Exception
Dec 9 23:21:25 box Bank 4: f62ba001c0080813 at 00000000a6e6c2c0
Dec 9 23:21:25 box Kernel panic: CPU context corrupt
Dec 9 23:21:25 box kernel: CPU 0
Dec 9 23:21:25 box kernel: CPU 0
Dec 9 23:21:25 box kernel: Bank 4
Dec 9 23:21:25 box kernel: Bank 4
Dec 9 23:21:25 box kernel: Kernel panic
Dec 9 23:21:25 box kernel: Kernel panic
Dec 9 23:21:26 box kernel BUG at panic.c:66!
Dec 9 23:21:26 box invalid operand: 0000
Dec 9 23:21:26 box CPU: 0
Dec 9 23:21:26 box EIP: 0010
Dec 9 23:21:26 box EFLAGS: 00010282
Dec 9 23:21:26 box eax: f895c1d0 ebx
Dec 9 23:21:26 box esi: 00000415 edi
Dec 9 23:21:26 box ds: 0018 es
Dec 9 23:21:26 box Process java (pid: 6852, stackpage=e0ec5000)
Dec 9 23:21:26 box Stack: 04000000 e0ec5fa4 c010fc28 c02942b8 00000005
c0080813 00000417 00000416
Dec 9 23:21:26 box 00000005 00000000 00000004 e0ec4000 00000000
c010fd00 e0ec5fb4 c010fd11
Dec 9 23:21:26 box e0ec5fc4 00000000 bfffc090 c0108ed4 e0ec5fc4
00000000 00000023 44841510
Dec 9 23:21:26 box Call Trace: [<c010fc28>] [<c010fd00>] [<c010fd11>]
[<c0108ed4>]
Dec 9 23:21:26 box
Dec 9 23:21:26 box Code: 0f 0b 42 00 28 6a 29 c0 b9 00 e0 ff ff 21 e1 8b
51 30 c1 e2
Thanks,
Justin.
next reply other threads:[~2006-03-10 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 11:44 Justin Piszcz [this message]
2006-03-11 9:51 ` Marco Roeland
2006-03-11 22:07 ` Justin Piszcz
2006-03-11 22:42 ` Randy.Dunlap
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=Pine.LNX.4.64.0603100642220.1165@p34 \
--to=jpiszcz@lucidpixels.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®