From: Felipe W Damasio <felipewd@terra.com.br>
To: Felix von Leitner <felix-kernel@fefe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Machine Check Exception
Date: Mon, 16 Dec 2002 19:55:58 +0000 [thread overview]
Message-ID: <3DFE2FCE.2000701@terra.com.br> (raw)
In-Reply-To: <20021215202227.GA7375@codeblau.de>
Felix von Leitner wrote:
> As soon as I start oggenc on my 2.5 kernel, I get this message:
>
> CPU 0: Machine Check Exception: 0000000000000004
> Bank 0: f60600000000135 at 000000001ea46db0
> Kernel panic: CPU context corrupt
>
> This vc then hangs, but I could log in and write down the message on
> another vc. Is this a hardware error? Should I replace my CPU? My
> memory? Is my machine overheating? I have had several strange and
> unexplained segfaults and reboots under 2.4 recently.
Looks like a instruction fetch error from the level 1 cache.
Your CPU may be overheating, yes. Or it could even be a faulty processor.
Could you please check your cooler? What's the average CPU temp.?
Felipe
next prev parent reply other threads:[~2002-12-16 21:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 20:22 Machine Check Exception Felix von Leitner
2002-12-15 20:39 ` Jan-Benedict Glaw
2002-12-16 19:55 ` Felipe W Damasio [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 11:05 machine check exception Nicholas Mucci
2003-12-03 13:05 ` Russell Coker
2003-12-03 13:19 ` Stephen Smalley
2008-10-05 17:41 Machine Check Exception Matteo Croce
2011-07-27 11:05 Machine check exception F. P. Beekhof
2011-07-27 13:03 ` Borislav Petkov
2011-07-27 15:31 ` F. P. Beekhof
2011-07-27 17:03 ` Borislav Petkov
2011-07-27 20:54 ` F. P. Beekhof
2011-07-27 21:30 ` F. P. Beekhof
2011-07-28 7:47 ` Borislav Petkov
2011-07-31 8:22 ` F. P. Beekhof
2011-07-31 12:09 ` Borislav Petkov
2011-07-31 15:56 ` F. P. Beekhof
2011-08-01 8:48 ` Borislav Petkov
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=3DFE2FCE.2000701@terra.com.br \
--to=felipewd@terra.com.br \
--cc=felix-kernel@fefe.de \
--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 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.