public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: MCEs
Date: Fri, 24 Oct 2008 23:44:22 +0200	[thread overview]
Message-ID: <20081024214422.GA20599@codeblau.de> (raw)
In-Reply-To: <87r66598eq.fsf@basil.nowhere.org>

> > This is the kind of MCE that freezes the box and causes a panic.  The
> > trace does not end up in syslog.  I found a program called mcelog which
> > I am supposed to call regularly from cron, but how can that help me when
> > the first MCE I get insta-panics the box?
> When you do a warm boot (not power cycle, but reset button or 
> panic=30) then the panic mce will be logged after reboot.

Maybe I'm doing something wrong here.
I run mcelog from the shell after the boot.
Nothing happens, I get the shell prompt right back.

How do I know it's really a MCE?  So far my symptoms are: the machine
freezes, then a panic dump scrolls by, and the only text I can see on my
screen are the stack dump lines, which contain something to the tune of
machine_check() or so.  Nothing shows up in syslog, probably the kernel
decides the box is too hosed to log anything.

Felix

  reply	other threads:[~2008-10-24 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 12:45 MCEs Felix von Leitner
2008-10-24 16:23 ` MCEs Tony Vroon
2008-10-24 18:04 ` MCEs Andi Kleen
2008-10-24 21:44   ` Felix von Leitner [this message]
2008-10-24 23:07   ` MCEs Felix von Leitner
2008-10-25  7:00     ` MCEs Andi Kleen
2008-10-25 10:05       ` MCEs Felix von Leitner

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=20081024214422.GA20599@codeblau.de \
    --to=felix-linuxkernel@fefe.de \
    --cc=andi@firstfloor.org \
    --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