* CPU context corrupt?
@ 2001-09-04 12:33 Aquila
2001-09-05 1:03 ` H. Peter Anvin
0 siblings, 1 reply; 2+ messages in thread
From: Aquila @ 2001-09-04 12:33 UTC (permalink / raw)
To: linux-kernel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: CPU context corrupt?
2001-09-04 12:33 CPU context corrupt? Aquila
@ 2001-09-05 1:03 ` H. Peter Anvin
0 siblings, 0 replies; 2+ messages in thread
From: H. Peter Anvin @ 2001-09-05 1:03 UTC (permalink / raw)
To: linux-kernel
Followup to: <999606788.1571.12.camel@hamlet>
By author: Aquila <aquila@hypox.org>
In newsgroup: linux.dev.kernel
>
> 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?
>
Yes.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-09-05 1:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-09-04 12:33 CPU context corrupt? Aquila
2001-09-05 1:03 ` H. Peter Anvin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox