kern/72979: unkillable process(es) stuck in `STOP' state
bde at zeta.org.au
Tue Feb 6 14:55:53 UTC 2007
Long ago, On Tue, 2 Jan 2007, David Xu wrote:
> The following reply was made to PR kern/72979; it has been noted by GNATS.
> On Tuesday 02 January 2007 03:12, Andrew Pantyukhin wrote:
> > I've got picard (a very fat python app) in this very
> > state, on latest current. I tried killing its parent
> > (zsh) which only reassigned it to ppid 1. I won't try
> > to kill that one :-)
> > Tell me I'm on crack or I'll reopen this PR.
> > Thanks!
> Can you reproduce it on 6.2 RC ?
This or something similar is still happening under 6.2-PRERELEASE-Dec-10-2006
(nosedive.freebsd.org). It seemed to be more common under 6.0. Stopping
a kernel compile used to cause lots of processes that seemed to be in
inifinite disk wait on nfs files. The stop (^Z and then ^C) doesn't
finish and the shell appears to be hung too, and cannot be killed
properly using SIGHUP. However, last time this happened I was able
to clear all the hung processes by sending SIGCONT from another shell
to some of the deeply nested ones.
I haven't seen this on any local machines, so it may be timing-related.
When it seemed to be happening more, I was running kernel builds with
excessive concurrency due to bugs in getting enough parallelism to
work around network latency, so it may be related to just running lots
of similar competing processes.
The recent patches don't seem to be in -current or RELENG_6.
More information about the freebsd-bugs