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 14:50:37 +0100 [thread overview]
Message-ID: <1022593837.4124.78.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0205281301440.27799-100000@buffy.commerce.uk.net>
On Tue, 2002-05-28 at 13:19, Corin Hartland-Swann wrote:
> I have a Dual PIII-1000 running 2.4.18, and am occasionally getting the
> following error:
>
> > CPU 1: Machine Check Exception: 000000000000000004
> > Bank 1: f200000000000115
> > Kernel panic: CPU context corrupt
>
> This results in a hard lock (unable to use magic SysRQ key to sync or
> reboot, etc). I located these errors in arch/i386/kernel/bluesmoke.c in
> the function intel_machine_check(). From what I have read on lkml it is
> probably a result of the processor overheating and causing errors.
It may even be a faulty processor. If you are running the processor to
spec and your heatsink/fan/voltage all check out you may want to see
about getting the CPU replaced. Thats a data cache l1 read error it
appears
> meantime is there anything I can do to get the machine to reboot after the
> panic? After the last time that this happened, I set
> /proc/sys/kernel/panic to 10, but it hasn't happened since then so I can't
> tell whether it will work. The error listed above is the entire error
> before the machine fails - there is no register dump or anything after
> that.
That /proc setting should cause a reboot although after an MCE all
things are a little undefined
> Do you think it will manage to reboot with a hopelessly confused
> processor?
Should do
next prev parent reply other threads:[~2002-05-28 12:48 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 [this message]
2002-05-28 13:46 ` Corin Hartland-Swann
2002-05-28 15:09 ` Alan Cox
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=1022593837.4124.78.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®