From: Aquila <aquila@hypox.org>
To: linux-kernel@vger.kernel.org
Subject: CPU context corrupt?
Date: 04 Sep 2001 22:33:08 +1000 [thread overview]
Message-ID: <999606788.1571.12.camel@hamlet> (raw)
Hi
I have had this problem quite a while now: when playing tribes2 or when
a particular CPU intensive xscreensaver is running, X would often hang.
I used to be able to ssh from another box or use SysRq-K to kill X and
restart (but I never figured out what the problem was).
Ever since upgrading to 2.4.9-ac3 (from 2.4.8-ac5 I believe), whenever
it hangs in X the computer would beep and give this message in syslog:
Sep 4 21:43:41 hamlet kernel: CPU 0: Machine Check Exception:
0000000000000004
Sep 4 21:43:41 hamlet kernel: Bank 1: f600200000000152 at
7600200000000152
Sep 4 21:43:41 hamlet kernel: Bank 2: d40040000000017a at
540040000000017a
Sep 4 21:43:41 hamlet kernel: Kernel panic: CPU context corrupt
It hangs there, and SysRq-K is no longer able to kill X properly. sshd
stops working as well. What does this message mean? Do I have faulty
hardware?
My CPU is an Athlon 1.2Ghz, not overclocked. Any ideas what's wrong?
Thanks,
Aq.
next reply other threads:[~2001-09-04 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 12:33 Aquila [this message]
2001-09-05 1:03 ` CPU context corrupt? H. Peter Anvin
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=999606788.1571.12.camel@hamlet \
--to=aquila@hypox.org \
--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