[lkml]   [2001]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectCPU context corrupt?

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:
Sep 4 21:43:41 hamlet kernel: Bank 1: f600200000000152 at
Sep 4 21:43:41 hamlet kernel: Bank 2: d40040000000017a at
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

My CPU is an Athlon 1.2Ghz, not overclocked. Any ideas what's wrong?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:02    [W:0.032 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site