All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Andersen <rasmus@jaquet.dk>
To: Felipe W Damasio <felipewd@terra.com.br>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.23-rc2 & an MCE
Date: Fri, 29 Nov 2002 07:18:03 +0100	[thread overview]
Message-ID: <20021129071803.A7602@jaquet.dk> (raw)
In-Reply-To: <3DE6A0A8.7080501@terra.com.br>; from felipewd@terra.com.br on Thu, Nov 28, 2002 at 11:03:04PM +0000

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

On Thu, Nov 28, 2002 at 11:03:04PM +0000, Felipe W Damasio wrote:
> Pavel Machek wrote:
> >>The MCE (hand copied):
> >>
> >>Machine Check Exception: 000000000000004
> >>Bank 4: b200000000040151
> >>Kernel panic: CPU context corrupt
> > 
> > Is not it trying to tell you about bad ram?
> 
> 	Could be, though this looks like a Instruction fetch error from the 
> Level 1 cache, doesn't it? If so, it could be caused by a faulty processor.
> 
> 	Is this the first time it happened? Could you please check your logs 
> and send any more MCE error codes?

Hi,

I have nothing in my logs but have had three more chrashes since
my first report. Two of them I couldn't inspect since I was at
work (the machine is at home) and had my girlfriend boot the box,
but the last one was identical to the reported one.

I am getting a new processor now and hope that'll do it.

Thanks for your comments,
  Rasmus

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-11-29  6:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 19:20 Linux 2.2.23-rc2 & an MCE Rasmus Andersen
2002-11-26 22:04 ` Pavel Machek
2002-11-28 23:03   ` Felipe W Damasio
2002-11-29  6:18     ` Rasmus Andersen [this message]
2002-11-29  7:18       ` Felipe W Damasio
2002-12-02  2:39   ` Randy.Dunlap
2002-12-02  9:26     ` Rasmus Andersen

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=20021129071803.A7602@jaquet.dk \
    --to=rasmus@jaquet.dk \
    --cc=felipewd@terra.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.