public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David King <dave@daveking.com>
To: linux-kernel@vger.kernel.org
Subject: Pls help me understand this MCE
Date: Thu, 11 Aug 2005 09:49:28 -0400	[thread overview]
Message-ID: <42FB5768.8070608@daveking.com> (raw)

I'm new at this so I'm learning my way through it and I'd appreciate any
guidance.  My system freezes solid intermittently for no apparent
reason.  The serial console shows a kernal panic caused by a machine
check exception.  mcelog decodes the MCE as follows:

CPU 0 4 northbridge TSC f03d1e587b
Northbridge Watchdog error
bit57 = processor context corrupt
bit61 = error uncorrected
bus error 'generic participation, request timed out
generic error mem transaction
generic access, level generic'
STATUS b200000000070f0f MCGSTATUS 4

That's all meaningless to me so I'm looking for help understanding what
it means and what parts of my system I should be looking at in order to
try to resolve this MCE.

A Google search found one hit that suggested that "Something tried to
access a physical memory address that was not mapped in the CPU."  If
that is indeed the correct interpretation, is there any wany to figure
out what that "something" is?

The system in question is a no-name system built from parts by a local
computer shop.  It has an ASUS A8N-SLI motherboard.  I have updated the
BIOS to the latest without affecting this problem.  The CPU installed is
an "AMD Athlon(tm) 64 Processor 3500+".  I am running Fedora Core 4,
kernel 2.6.12-1.1398_FC4.

Any guidance would be appreciated.

-- 
David King
dave@daveking.com

             reply	other threads:[~2005-08-11 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 13:49 David King [this message]
2005-08-11 14:10 ` Pls help me understand this MCE Petr Vandrovec
2005-08-11 18:02   ` David King

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=42FB5768.8070608@daveking.com \
    --to=dave@daveking.com \
    --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