Recently I decided to upgrade from kernel version 2.27.7 to 2.28.4 in an effort to fix some PS/2 mouse troubles (random erratic behavior not fixed by any other method). However, when I first booted up with the new kernel, I received this error:
CPU0: Machine Check Exception: 0000000000000004
CPU0: Bank 4: 3200000000070f0f
Kernel panic - not syncing: CPU context corrupt
Now I know that this is a MCE error and that it's "correctable" by either recompiling the kernel without support for the checking, or by passing "nomce" to my kernel at the lilo prompt.
What I noticed that was strange about this was that once I booted up with the older kernel, started using a USB mouse, recompiled the kernel without some CPU options (mainly those pertaining to Athlon 64), and rebooted with that new kernel, everything worked fine. But when I plugged in my either of my PS/2 mice while the computer was running, it wouldn't work. Reloading the psmouse kernel module did nothing.
When I rebooted again with the PS/2 mouse plugged in, I got the same kernel panic as above.
I tried this several more times and indeed, it was just the PS/2 mouse being plugged in a boot time that caused the error.
The two PS/2 mice that I used are:
- Belkin 3-button "Serial & PS/2 Mouse" (switch on bottom with the options PC AT and MS AM)
- no-name two-button wireless mouse w/ scroll wheel
Currently I'm using an Apple mouse (with only one button!) and while usable, it's quite a pain without at least one other button.
I'm currently running on an Athlon 64 3000+, 1.25G of [working] RAM, and a Giga-byte K8NS-Ultra 939 motherboard.
So what could be causing a kernel panic when the only thing that changes is the addition of a PS/2 mouse?
I will post any other information needed.