From: Michael Klemm (michael.klemm_at_informatik.uni-erlangen.de)
Date: Fri Feb 25 2005 - 01:51:29 PST
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Paul H. Hargrove wrote: | The one thing that confuses me is the fact that some uniterruptible | process was consuming 100% of CPU. There should be no spin waits in the | kernel's checkpoint or restart code paths, so this may be an indication | of a larger problem. There is a spinwait for thread synchronization in | user space that you may have encountered. At that point the process | probably has all signals blocked, making it *almost* uninterruptible. | Could you please determine if sending SIGKILL (an unblockable signal) is | capable of killing the cpu-consuming process? That would narrow down | some things for me. I've checked SIGTERM, SIGKILL and some other signals. None was able to terminate the process. It looks like the process is trapped inside the kernel and is not able to get back from there. A "ps aux" on the machine confirms this: | root 6841 0.0 0.4 8124 2500 ? Ss 10:46 0:00 sshd: admin@pts/2 | root 6844 0.0 0.3 2460 1568 pts/2 Ss 10:46 0:00 -bash | klemm 6909 79.7 0.0 0 0 pts/1 R+ 10:48 0:16 [cr_restart] | root 6928 0.0 0.1 2164 688 pts/2 R+ 10:48 0:00 ps aux Regards -michael - -- Computer Science Department 2, University of Erlangen-Nuremberg Martensstrasse 3, D-91058 Erlangen, Germany phone: ++49 (0)9131 85-28995, fax: ++49 (0)9131 85-28809 web: http://www2.informatik.uni-erlangen.de/~klemm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCHvUhWEu1syWqdn0RApNgAKDAtxDxj56d7RfDkoBiRjKFX9vcXACgtS2+ yURiMixI+bMX/D1kanMTpt0= =YVsG -----END PGP SIGNATURE-----