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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
