Messages in this thread | | | Date | Fri, 20 Oct 2006 23:30:49 -0400 | From | Dave Jones <> | Subject | Re: Machine Check Exception on dual core Xeon |
| |
On Tue, Oct 17, 2006 at 09:43:20PM -0400, Kyle Moffett wrote: > On Oct 17, 2006, at 19:34:59, Steven Truong wrote: > > Hi, all. I have this node of dual core Xeon 3.2 GHz, 4 Gig of RAM and > > kernel 2.16.18 on CentOS 4.3. I got kernel panic and after setting up > > kdump/kexec I was able to capture the kdump core. > > I found out this message with crash to analyze the core dump: > > > > HARDWARE ERROR > > CPU 0: Machine Check Exception: 4 Bank 3: > > 0000000000000000 > > TSC 0 > > This is not a software problem! > > Run through mcelog --ascii to decode and contact your hardware vendor > > You missed the blatantly obvious error message: > "This is not a software problem!" > > Immediately followed by: > "contact your hardware vendor" > > Please follow that advice
Maybe someone needs to implement <blink> tags for printk ;-)
Dave
-- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |