From: Alex Riesen <fork0@users.sourceforge.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.18-pre8-K2: Kernel panic: CPU context corrupt
Date: Fri, 8 Feb 2002 23:13:05 +0100 [thread overview]
Message-ID: <20020208231305.B13545@steel> (raw)
In-Reply-To: <20020208001831.A200@steel> <20020208003653.A28235@suse.de>
In-Reply-To: <20020208003653.A28235@suse.de>
On Fri, Feb 08, 2002 at 12:36:53AM +0100, Dave Jones wrote:
> On Fri, Feb 08, 2002 at 12:18:31AM +0100, Alex Riesen wrote:
>
> > Feb 7 23:45:31 steel kernel: CPU 0: Machine Check Exception: 0000000000000004
> > Feb 7 23:45:31 steel kernel: Bank 4: b200000000040151
> > Feb 7 23:45:31 steel kernel: Kernel panic: CPU context corrupt
>
> Machine checks are indicative of hardware fault.
> Overclocking, inadequate cooling and bad memory are the usual causes.
no overclocking, memtest passed (1 pass, 1 hour), native intel cooler.
Space radiation, maybe 8)
> > P.S. no nasty suspections about processor, please. No funds reserved
> > for a new one :)
>
> The truth hurts 8(
oh dear...
>
> --
> | Dave Jones. http://www.codemonkey.org.uk
> | SuSE Labs
next prev parent reply other threads:[~2002-02-08 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 23:18 2.4.18-pre8-K2: Kernel panic: CPU context corrupt Alex Riesen
2002-02-07 23:36 ` Dave Jones
2002-02-08 22:13 ` Alex Riesen [this message]
2002-02-09 22:23 ` Pavel Machek
2002-02-10 21:33 ` Dave Jones
2002-02-11 1:03 ` Alan Cox
2002-02-11 11:59 ` Alex Riesen
2002-02-11 12:52 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
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=20020208231305.B13545@steel \
--to=fork0@users.sourceforge.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