kern/72979: unkillable process(es) stuck in `STOP' state

[Mark Wolgemuth]

The following reply was made to PR kern/72979; it has been noted by GNATS.

From: Mark Wolgemuth <mark at employease.com>
To: freebsd-gnats-submit at FreeBSD.org
Cc:  
Subject: Re: kern/72979: unkillable process(es) stuck in `STOP' state
Date: Tue, 12 Apr 2005 12:34:58 -0400

 I just had this 'STOP' thread unkillable proc behavior with this setup:
 
 5.3-RELEASE-p7
 
 My kernel is GENERIC + SMP option + ipfw options.
 
 I run these packages inside a jail. The jail is a clone of the host 
 system, plus the packages.
 The host system has only the cyrus-sasl pkgs to support smtp/auth, 
 nothing else. The jail has these:
 
 pkg: spamass-milter:
 spamass-milter-0.2.0_5
 
 pkgs for spamassassin:
 p5-Digest-HMAC-1.01 Perl5 interface to HMAC Message-Digest Algorithms
 p5-Digest-SHA1-2.10 Perl interface to the SHA-1 Algorithm
 p5-HTML-Parser-3.38 Perl5 module for parsing HTML documents
 p5-HTML-Tagset-3.04 Some useful data table in parsing HTML
 p5-Mail-SpamAssassin-3.0.2 A highly efficient mail filter for 
 identifying spam
 p5-Mail-Tools-1.66  Perl5 modules for dealing with Internet e-mail 
 messages
 p5-Net-DNS-0.48     Perl5 interface to the DNS resolver, and dynamic 
 updates
 p5-URI-1.35         Perl5 interface to Uniform Resource Identifier 
 (URI) refere
 perl-5.8.6_2        Practical Extraction and Report Language
 
 The error occured between "spamass-milter", which uses libkse for 
 threads, and spamc, a child process that communicates to spamd. They 
 share a socket file.
 It appears that a thread spawned a spamc process that hung.
 
 Attempting to kill the process for spamass-milter left all threads in 
 "STOP" state. Attempting to kill spamc proc left a <defunct>. At this 
 point I was stuck and (stupidly) tried attaching gdb to spamass-milter, 
 which locked the entire system.