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

[Ken Smith]

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

From: Ken Smith <kensmith at cse.Buffalo.EDU>
To: Mikhail Teterin <mi+mx at aldan.algebra.com>
Cc: Ken Smith <kensmith at cse.Buffalo.EDU>,
	David Xu <davidxu at freebsd.org>,
	Michael Nottebrock <michaelnottebrock at gmx.net>, re at freebsd.org,
	davidxu at t2t2.com, davidxu at viatech.com.cn,
	freebsd-gnats-submit at freebsd.org
Subject: Re: kern/72979: unkillable process(es) stuck in `STOP' state
Date: Wed, 27 Oct 2004 14:23:40 -0400

 On Tue, Oct 26, 2004 at 12:07:47PM -0400, Mikhail Teterin wrote:
 > =On Tue, Oct 26, 2004 at 07:11:54PM +0800, David Xu wrote:
 > =That looks both promising (given symptoms) and low-risk.
 > =
 > =Mikhail et. al., will you have any problems testing that?
 > 
 > This problem was not easy to reproduce to begin with :-(
 > 
 > I don't even know, how it can be positively claimed gone. Shall we merge 
 > David's fix into RELENG_5 and hope for the best?
 > 
 >  -mi
 
 Has anyone had time to test David's patch?  If yes have you had
 any problems since?
 
 I should know later today if the other person who had been reporting
 problems has had them stop.  He reported last night he was still able
 to reproduce the problem but he hasn't had any "luck" doing it today.
 
 David, my only real question I guess is whether perhaps	P_STOPPED_SINGLE
 should be added to the flags that are being turned off by your patch.
 If I'm following the code right what had made P_STOPPED_TRACE special
 was it's one of the three signals lumped into P_STOPPED and the code
 in do_tdsignal() looks for that, as well as I'm sure the schedulers...
 
 -- 
 						Ken Smith
 - From there to here, from here to      |       kensmith at cse.buffalo.edu
   there, funny things are everywhere.   |
                       - Theodore Geisel |