Earlier today, while in X and doing routine stuff in multiple xterms, my
mouse locked up on me and the machine stopped responding to any input from
the console. I was able to login to my locked up workstation from another
machine on the network. I couldn't see anything wrong and after about 30
seconds I could use X again.
Everything worked fine once more for more than an hour. Then it
happened again. This time X did not return. After a few minutes my load
average climbed to 3.00 (I was running two instances of rc5des). I could
not find the third process that was running. I killed the two rc5deses
and now the load average is sitting at 1.00. Its been like this for a
couple of hours now. The machine is unusable at the console, but is
otherwise working just fine. I thought that X might be stuck and was
chowing 100% of a CPU, but it doesn't appear to be using any CPU at all
and I still can't find the process causing the load of 1.00. I suspect
that it is somehow the kernel that has gotten stuck. I've tried kill
-9'ing X, but it won't die.
Any thoughts?
My setup:
Micronics W6-Li with two PPro 180's
64MB RAM
Debian Linux 2.1
kernel 2.2.26
no brainer NE2000 NIC
IDE disks (no SCSI)
Hercules Stingray 128/3D video
My uptime was over 30 days without the slightest problem.
Since it looks like I'm going to have to reboot to get my console back
I'll probably just upgrade to 2.2.10, wait a month and see if it happens
again. I'd love to hear anyone's ideas on what has happened here.
Thanks,
-M@
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
