public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Steven Truong <midair77@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Machine Check Exception on dual core Xeon
Date: Fri, 20 Oct 2006 23:30:49 -0400	[thread overview]
Message-ID: <20061021033049.GC17706@redhat.com> (raw)
In-Reply-To: <90DB029B-222B-4D0C-8642-913CD81D5C9B@mac.com>

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

  reply	other threads:[~2006-10-21  3:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 23:34 Machine Check Exception on dual core Xeon Steven Truong
2006-10-17 23:54 ` Steven Truong
2006-10-18  1:43 ` Kyle Moffett
2006-10-21  3:30   ` Dave Jones [this message]
2006-10-28  5:27     ` Randy Dunlap
2006-10-28  6:29       ` Dave Jones
2006-10-28 15:51         ` 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=20061021033049.GC17706@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=midair77@gmail.com \
    --cc=mrmacman_g4@mac.com \
    /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