Last night our load average jumped and stayed at around 3. top did not
show any noticeable activity.
Eventually we noticed 3x in.ntalkd processes. These were stuck in the "D"
state and accounting for the load average.
There were waiting in "__do_down" for some unknown semaphore I presume!!
Eventually they were persuaded to go away when we killed an idle bash(!!).
The bash involved would have spawned one of the ytalk's associated with
the in.ntalkd processes.
So..
1) Why was our load average contributed to?
2) What on earth could the in.ntalkd's possibly have been waiting on in
uninterruptible sleep that freed up when the bash process exited? Some
weird tty layer thing?
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu