From owner-freebsd-current@FreeBSD.ORG Thu Nov 4 20:47:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E953316A4CE; Thu, 4 Nov 2004 20:47:26 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6B2943D54; Thu, 4 Nov 2004 20:47:24 +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 83EE67A43E; Thu, 4 Nov 2004 12:47:24 -0800 (PST) Message-ID: <418A955C.9080704@elischer.org> Date: Thu, 04 Nov 2004 12:47:24 -0800 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: Marc Ramirez References: <200411020143.34251.gte990t@mail.gatech.edu> <20041104144605.GF24440@electra.cse.Buffalo.EDU> <418A73FD.2070201@elischer.org> <200411041525.51985.marc.ramirez@bluecirclesoft.com> In-Reply-To: <200411041525.51985.marc.ramirez@bluecirclesoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: re@freebsd.org cc: Ken Smith Subject: Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 20:47:27 -0000 > thread 0xc2081e10 ksegrp 0xc2154310 [SUSP] > thread 0xc187a960 ksegrp 0xc2154310 [SLPQ spltwt 0xc138fd98][SLP] > thread 0xc2156960 ksegrp 0xc2154310 [SUSP] > thread 0xc2157000 ksegrp 0xc2154310 [SUSP] > thread 0xc2157190 ksegrp 0xc2154310 [SLPQ select 0xc08e44c4][SLP][SUSP] > thread 0xc2156190 ksegrp 0xc2154310 [SLPQ accept 0xc216ae26][SLP][SUSP] > thread 0xc2156320 ksegrp 0xc187dc40 [SUSP] > > > > showing the output of show thread 0xc2081e10 (etc) for each thread should show the backtrace of each thread (I think) it would be instructive to see where each thread is.. I suspect that all the threads are waiting for thread 0xc187a960 to wake up and suspend for some single-threading purpose. but it is hard to tell. > > > >