public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <fork0@users.sourceforge.net>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.18-pre8-K2: Kernel panic: CPU context corrupt
Date: Mon, 11 Feb 2002 12:59:02 +0100	[thread overview]
Message-ID: <20020211125902.B3342@steel> (raw)
In-Reply-To: <20020208001831.A200@steel> <20020208003653.A28235@suse.de> <20020209222358.GA1589@elf.ucw.cz>
In-Reply-To: <20020209222358.GA1589@elf.ucw.cz>

I can good understand that it is a hardware problem.
But if someone seems not to be interested in reports like this,
why dump them out? Just save what we can and hang silently,
but no reports, they're boring 8-]


What does the "Bank 4: b200000000040151" mean?
If that is a memory, can anyone help to find out which slot it is?
(memtest86 haven't found anything, btw, i doubt that counts)
-alex

P.S. if someone going to change the message about machine check,
could you please avoid lame descriptions? Like "(hardware problem!)"?
I sure the majority are experienced enough to understand what the
words "Machine Check" mean.


On Sat, Feb 09, 2002 at 11:23:58PM +0100, Pavel Machek wrote:
> Hi!
> 
> >  > 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.
> 
> Maybe you should print something like
> 
> Machine Check Exception: .... (hardware problem!)
> 
> so that we get less reports like this?
> 									Pavel
> -- 
> (about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
> no longer is classifiable as a democracy, but rather as a plutocracy." --hpa

  parent reply	other threads:[~2002-02-11 12:09 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
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 [this message]
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=20020211125902.B3342@steel \
    --to=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