From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Unable to kill processes in D-state
Date: 05 Oct 2002 14:11:02 -0400 [thread overview]
Message-ID: <1033841462.1247.3716.camel@phantasy> (raw)
In-Reply-To: <20021005090705.GA18475@stud.ntnu.no>
On Sat, 2002-10-05 at 05:07, Thomas Langås wrote:
> 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
next prev parent reply other threads:[~2002-10-05 18:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 9:07 Unable to kill processes in D-state Thomas Langås
2002-10-05 18:11 ` Robert Love [this message]
2002-10-05 18:27 ` Jan Hudec
2002-10-05 23:56 ` Thomas Langås
2002-10-06 2:18 ` jw schultz
2002-10-06 2:37 ` Robert Love
2002-10-06 2:49 ` jw schultz
2002-10-06 10:59 ` Thomas Langås
2002-10-06 12:24 ` jw schultz
2002-10-06 14:36 ` Thomas Langås
2002-10-06 16:42 ` Jan Hudec
2002-10-06 17:09 ` Thomas Langås
2002-10-06 17:43 ` Jan Hudec
2002-10-07 12:24 ` Denis Vlasenko
2002-10-16 0:33 ` Thomas Langås
2002-10-06 14:30 ` Graham Murray
2002-10-06 14:54 ` Thomas Langås
2002-10-06 20:26 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1033841462.1247.3716.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox