It was running X and it just stopped responding to the keyboard.
It's happened a few times recently, even before the aic7xxx driver upgrade.
I still had mouse, and Alt-SysRq functions. Previous experience has been that
I'm able to cut and paste into a talk session, if I have the patience to find
the letters I require on-screen. When I finally managed to convey my SOS to the
person at the other end, no TCP connections were being answered. The kernel was
connecting the TCP socket, but inetd was not managing to fork the daemons.
Serial lines were down, too - there was no response to the serial terminal at
the other side of the room.
The MDA syslog monitor (patched to be a console, so anything printk'd would
have been there) said nothing.
Alt-SysRq-P showed PC values looping closely:
c011a4ea
c011a508
c011a404
> c011a370 t exit_notify
> c011a5d0 T do_exit
c01ba2d7
c01ba2c3
> c01ba2b0 T __lock_kernel
> c01ba2ec T __delay
For more hardware/kernel details, look at
http://dwmw2.robinson.cam.ac.uk/cgi-bin/dmesghtml
--
---- ---- ----
David Woodhouse, Robinson College, CB3 9AN, England. (+44) 0976 658355
Dave@imladris.demon.co.uk http://dwmw2.robinson.cam.ac.uk
finger pgp@dwmw2.robinson.cam.ac.uk for PGP key.