From: Dave Jones <davej@suse.de>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Marcel Kunath <kunathma@pilot.msu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Machine Check Exception ?
Date: Fri, 25 Jan 2002 18:22:40 +0100 [thread overview]
Message-ID: <20020125182240.I28068@suse.de> (raw)
In-Reply-To: <20020125114718.7af47375.skraw@ithnet.com> <200201251237.g0PCbOR17328@pilot05.cl.msu.edu> <20020125173623.03923d29.skraw@ithnet.com>
In-Reply-To: <20020125173623.03923d29.skraw@ithnet.com>; from skraw@ithnet.com on Fri, Jan 25, 2002 at 05:36:23PM +0100
On Fri, Jan 25, 2002 at 05:36:23PM +0100, Stephan von Krawczynski wrote:
> It boots and runs for quite a while (weeks), then suddenly freezes and
> shows this message.
> It does not happen often, but very rarely.
> Has the number any meaning, or is it a goof?
> > > diehard kernel: CPU 0: Machine Check Exception: 0000000000000004
This number alone doesn't really tell anything.
There should be an extra line in the log / on the console,
which contains two more 64bit numbers. Putting these into
http://www.codemonkey.org.uk/cruft/parsemce.c will decode
them and give you more idea hopefully over whats wrong.
(I really should make that tool a little friendlier ..
I'll do it soon)
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-25 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 10:47 Machine Check Exception ? Stephan von Krawczynski
2002-01-25 12:37 ` Marcel Kunath
2002-01-25 16:36 ` Stephan von Krawczynski
2002-01-25 17:22 ` Dave Jones [this message]
2002-01-25 16:47 ` Stephan von Krawczynski
2002-01-25 12:40 ` Denis Oliver Kropp
2002-01-25 13:17 ` Dave Jones
2002-01-25 13:26 ` Denis Oliver Kropp
-- strict thread matches above, loose matches on Subject: below --
2002-01-25 18:37 Dana Lacoste
2002-01-25 18:48 ` Dave Jones
2005-12-27 2:52 Machine Check Exception ! Legend W.
2005-12-27 6:46 ` Nauman Tahir
2005-12-27 17:51 ` Lee Revell
2005-12-31 1:04 ` Alan Cox
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=20020125182240.I28068@suse.de \
--to=davej@suse.de \
--cc=kunathma@pilot.msu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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