> We have a fairly large installation on-campus, and we have some problems
> with the current linux-kernel (and older ones) - namely that processes
> entering D-state will stay there forever (given that the right event got
> them there in the first place). This right event is killing the
> autofs-daemon. Doing this will result in heavy load because of lots
> of D-state processes, and you can't kill any of the D-state processes.
> Why shouldn't one be able to kill processes that has entered D-state?
> We have to reboot our servers to get rid of this problem, and it's
> rather annoying.
Because they are in uninterruptible sleep. They are doing something
important, presumably in a critical section, and have no wake-up path
for signals or errors.
Finally, they probably hold a semaphore. In short, you cannot kill
them, nor would you want to.
I would simplify the question and ask why are you killing the autofs
daemon? Clearly this is a recipe for disaster.
Robert Love
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ction called from illegal context at"