[svlug] 2.1.127/8 weirdness?

[Bevan Schroeder]

On Sat, 14 Nov 1998, George Bonser wrote:

> Example: I could have knews up and I can read news just fine. If I go to a
> command prompt and issue an uptime command, it can take 10 minutes to
> respond. In the meantime, there is no disk activity or anything. 

Some things to try...

1. strace it.  It sounds like it might be stalling in fork() or exec().
stracing everything would probably get old pretty fast though.

2. have top running, with WCHAN output, to see where the process is stuck
in the kernel (for WCHAN to work, you should put
/usr/src/linux/System.map in /lib/modules/<ver>/ or similar, for top to
find it.  I should probably resend my top patch, it never made it in...)

3. use the sysrq keys to find out what's going on.  't' is probably best,
it lists all the processes currently running, have to look up the IP in
System.map manually.  There is info on the sysrq keys in 
/usr/src/linux/Documentation/.  Or you can just hit alt-sysrq-h if you're
feeling adventurous.

-bevan


--
echo "unsubscribe svlug" | mail majordomo at svlug.org
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ to unsubscribe