From: Tom Vier <tmv@comcast.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Deadlocks and Machine Check Exception on Athlon64
Date: Thu, 19 Feb 2004 20:06:23 -0500 [thread overview]
Message-ID: <20040220010623.GA14838@zero> (raw)
In-Reply-To: <1077229909.2828.22.camel@terminal124.gozu.lan>
On Thu, Feb 19, 2004 at 11:31:50PM +0100, Ronny V. Vindenes wrote:
> CPU 0: Machine Check Exception : 0000000000000004
> Bank 4: b200000000070f0f
> kernel panic: CPU context corrupt
> In interrupt handler - not syncing
i've gotten the same machine check a couple times. it only happened the
first few days i had my machine. i updated to the latest tyan bios which
fixes some bugs. i haven't had it happen since.
if i'm reading it right (which is hard on this small screen, slow cpu
laptop), page 153 of the opteron kernel/bios guide says this is an ecc data
cache exception (which is always fatal/nonrecoverable). this sounds like
errata 86, which is fixed in the tyan bios update i installed.
does msi say their 2.1 bios fixes #86?
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0xE6CB97DA
prev parent reply other threads:[~2004-02-20 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 22:31 Deadlocks and Machine Check Exception on Athlon64 Ronny V. Vindenes
2004-02-20 1:06 ` Tom Vier [this message]
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=20040220010623.GA14838@zero \
--to=tmv@comcast.net \
--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.