mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Corin Hartland-Swann <cdhs@commerce.uk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bluesmoke, machine check exception, reboot
Date: 28 May 2002 16:09:00 +0100	[thread overview]
Message-ID: <1022598540.4123.89.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0205281432450.27799-100000@buffy.commerce.uk.net>

On Tue, 2002-05-28 at 14:46, Corin Hartland-Swann wrote:
> CPU 1: Machine Check Exception: 0000000000000004
> Bank 1: b200000000000115
> Kernel panic: CPU context corrupt
>
> How do you work out what the numbers mean? Is there some kind of reference
> to it, or are you just Alan "decodes machine check exceptions in his head"
> Cox :) From the code it seems to be some kind of MCG status and MC0 status
> - but of course, I have no idea what that means...

I contemplate them in zen peace and they speak to me 8). The MCE value
is the flags from the control register. The Bank n value is a dump of
the register that explains what the fault is. The decoding rules are in
the Intel Pentium III documentation set.

> After checking the logs (above) I found that the two times this has
> happened it has managed to write it to the logs. Is the fact that it
> sync()d a good indication that it will manage to reboot OK?

Is the fact the airbag deployed a good indication that it will deploy if
you keep crashing into walls ? Its logging a CPU error where it decides
the CPU is in an unrecoverable state. The odds are pretty good but each
time you are taking the risk it won't, and if its a hardware problem
that it might simply drop dead for good.

Alan


  reply	other threads:[~2002-05-28 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 12:19 Corin Hartland-Swann
2002-05-28 13:50 ` Alan Cox
2002-05-28 13:46   ` Corin Hartland-Swann
2002-05-28 15:09     ` Alan Cox [this message]
2002-05-28 15:13     ` Randy.Dunlap
2002-05-29 13:46       ` Corin Hartland-Swann
2002-05-29 15:08         ` Dave Jones

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=1022598540.4123.89.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cdhs@commerce.uk.net \
    --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

all inboxes | Powered by JetHome®