Strange lockups on 2.4.2

[Steven Walter]

This has happened twice, now, though I don't believe its completely
reproduceable.  What happens is an Oops, which drops me into kdb.  I've
been in X both times, however, which makes kdb rather useless.  I
blindly type "go", and interrupts get reenabled, at least (I know
because my mp3 stops looping and begins playing again).  This almost
must mean at least part of userspace survives.  Probably only X dies,
since VT switching and numlock-toggling doesn't work.  I can Ctrl+SysRq
S-U-B, though.

The thing I find most interesting about this is that only 4 lines of the
oops gets into the log.  4 lines, both times.  This time, those lines
were:

 printing eip:
c0112e1f
Oops: 0002
CPU:    0

This corresponds to schedule according to System.map (that's the nearest
symbol without going over).  Before I believe it was path_walk.  If
anyone's got an idea, it'd be helpful.  Btw, this machine consistently
passes memtest, most recently ran 2 passes of all tests with no errors
found.
-- 
-Steven
Freedom is the freedom to say that two plus two equals four.