Date: Fri, 24 Oct 2008 23:44:22 +0200
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
Message-ID: <20081024214422.GA20599@codeblau.de>
References: <20081024124502.GA9425@codeblau.de> <87r66598eq.fsf@basil.nowhere.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87r66598eq.fsf@basil.nowhere.org>
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1119
Lines: 23

> > 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
--
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/