Bug 121062 - Freeze -- Machine Check Exception
Summary: Freeze -- Machine Check Exception
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 1
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-04-16 16:40 UTC by Elijah Newren
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-19 15:58:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Elijah Newren 2004-04-16 16:40:24 UTC
Description of problem:
I was just working on the computer (compiling gtkmm in a terminal
while working with Mozilla), when the system froze with the Caps Lock
and Scroll Lock lights blinking.  After rebooting (it rebooted fine
and seems to be working okay now), I checked /var/log/messages and saw

Apr 16 10:13:13 Eenie kernel: CPU 0: Machine Check Exception:

The line before that was dated over an hour before and appears
unrelated.  The line after that in the log corresponds to when I
rebooted and thus is also unrelated.

Version-Release number of selected component (if applicable):
'rpm -q kernel' reports  kernel-2.4.22-1.2115.nptl

How reproducible:
This is the First Time I've Ever Seen It (TM).

Additional info:
What other information would you need?  If this indicates there's
something wrong with my system, what kind of diagnostics should I run?

Comment 1 Sahil Verma 2004-04-16 21:59:08 UTC
This is likely a hardware problem - CPU or memory, even mobo. Keep
stressing by compiling gtkmm or kernel, you should be able to
reproduce the MCE.

Comment 2 Elijah Newren 2004-06-19 16:20:47 UTC
Sorry for not responding sooner.  I tried stressing it a couple times,
but didn't see the error/warning again.  I guess I should have closed
it myself.  Sorry about that.  Anyway, thanks for the quick response.
 Hopefully it was just a one-time fluke, though I won't be surprised
if it comes up again...

Note You need to log in before you can comment on or make changes to this bug.