linux-kernel - Re: Machine Check Exception on dual core Xeon

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061021033049.GC17706@redhat.com>
Date:	Fri, 20 Oct 2006 23:30:49 -0400
From:	Dave Jones <davej@...hat.com>
To:	Kyle Moffett <mrmacman_g4@....com>
Cc:	Steven Truong <midair77@...il.com>, linux-kernel@...r.kernel.org
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/