From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Orion Poplawski <orion@cora.nwra.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help with machine check exception
Date: Thu, 12 Jan 2006 17:33:53 +0000 [thread overview]
Message-ID: <1137087233.26334.3.camel@localhost.localdomain> (raw)
In-Reply-To: <dq62df$gse$1@sea.gmane.org>
On Iau, 2006-01-12 at 10:07 -0700, Orion Poplawski wrote:
> mcelog decode states:
>
> CPU 0 4 northbridge TSC 184fcd0553e4
> 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
> Kernel panic - not syncing: Machine check
Could be ram cpu or motherboard, even a power glitch of course.
Before you panic I'd suggest that you check the machine is being
adequately cooled (especially the CPU) and that the ram and cpu are all
well socketed.
memtest86+ will help test for memory problems and may be worth an
overnight run
next prev parent reply other threads:[~2006-01-12 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 16:30 Help with machine check exception Orion Poplawski
2006-01-12 17:07 ` Orion Poplawski
2006-01-12 17:33 ` Alan Cox [this message]
2006-01-12 17:52 ` Orion Poplawski
2006-01-12 19:18 ` Roger Heflin
2006-01-12 17:32 ` Roger Heflin
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=1137087233.26334.3.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=orion@cora.nwra.com \
/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