From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davej@suse.de (Dave Jones)
Cc: pavel@suse.cz (Pavel Machek),
fork0@users.sourceforge.net (Alex Riesen),
linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: 2.4.18-pre8-K2: Kernel panic: CPU context corrupt
Date: Mon, 11 Feb 2002 01:03:23 +0000 (GMT) [thread overview]
Message-ID: <E16a4sN-0004yi-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33.0202102232510.29486-100000@Appserv.suse.de> from "Dave Jones" at Feb 10, 2002 10:33:49 PM
> > Maybe you should print something like
> > Machine Check Exception: .... (hardware problem!)
> > so that we get less reports like this?
>
> When I get around to finishing the diagnosis tool, I'll add
> something like "Feed to decodemca for more info".
For a lot of processors the MCE values are not documented. Strangely for
once Intel are the good guys and AMD seem to be sitting on the docs.
next prev parent reply other threads:[~2002-02-11 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 23:18 Alex Riesen
2002-02-07 23:36 ` Dave Jones
2002-02-08 22:13 ` Alex Riesen
2002-02-09 22:23 ` Pavel Machek
2002-02-10 21:33 ` Dave Jones
2002-02-11 1:03 ` Alan Cox [this message]
2002-02-11 11:59 ` Alex Riesen
2002-02-11 12:52 ` Pavel Machek
2002-02-08 22:44 Dieter Nützel
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=E16a4sN-0004yi-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=fork0@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®