From owner-freebsd-threads@FreeBSD.ORG Wed Sep 8 18:55:52 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 969A016A4CF for ; Wed, 8 Sep 2004 18:55:52 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DD6443D31 for ; Wed, 8 Sep 2004 18:55:52 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 2A4787A3D2; Wed, 8 Sep 2004 11:55:52 -0700 (PDT) Message-ID: <413F55B8.50003@elischer.org> Date: Wed, 08 Sep 2004 11:55:52 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Andrew Gallatin References: <16703.11479.679335.588170@grasshopper.cs.duke.edu> <16703.12410.319869.29996@grasshopper.cs.duke.edu> In-Reply-To: <16703.12410.319869.29996@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org Subject: Re: Unkillable KSE threaded proc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2004 18:55:52 -0000 it is possible. Howevr you should try this on -current, (please) because I rewrite some of the exit code and may have already fixed it.. a -curent kernel can run a 5.3 userland in general so you may just need to recompile the kernel. Andrew Gallatin wrote: >Andrew Gallatin writes: > > > > If I send a kill -9 to a threaded process in a creative way, I see it > > get stuck forever exiting. (run from a /bin/sh script, > > killed via ssh $MACHINE skill -9 -u gallatin) > > > > It shows up in a ddb ps like this: > > > > 3403 c1652540 e52fe000 1387 1 3401 000c402 (threaded) mx_pingpong > > thread 0xc2de4c60 ksegrp 0xc15b2200 [SUSP] > > > > >FWIW, before sending it an skill -9, another run of the same program >will show up in ddb ps like this: > >3514 c1b65540 e6842000 0 3058 3514 000c002 (threaded) mx_pingpong > thread 0xc2e0ab00 ksegrp 0xc1b60100 [SLPQ kserel 0xc1b6015c][SLP] > thread 0xc1af7840 ksegrp 0xc1b60100 [CPU 1][kse 0xc1af8c00] > thread 0xc2de5840 ksegrp 0xc1b60100 [SLPQ mx cv 0xc16b9e40][SLP] > thread 0xc2de56e0 ksegrp 0xc2de3800 [SLPQ ksesigwait 0xc1b65640][SLP] > > >Since there's only one thread left in the hung case, could it just >be some sort of race in the exit code? > >Thanks, > >Drew > >