From owner-freebsd-current@FreeBSD.ORG  Mon Nov 15 21:18:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 40B7116A4CE
	for <current@FreeBSD.org>; Mon, 15 Nov 2004 21:18:55 +0000 (GMT)
Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CEB5743D45
	for <current@FreeBSD.org>; Mon, 15 Nov 2004 21:18:54 +0000 (GMT)
	(envelope-from jhb@FreeBSD.org)
Received: (qmail 10245 invoked from network); 15 Nov 2004 21:18:54 -0000
Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx)
	([216.27.160.63])          (envelope-sender <jhb@FreeBSD.org>)
	encrypted SMTP
	for <current@FreeBSD.org>; 15 Nov 2004 21:18:54 -0000
Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1])
	(authenticated bits=0)
	by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFLIlvv076672;
	Mon, 15 Nov 2004 16:18:50 -0500 (EST)
	(envelope-from jhb@FreeBSD.org)
From: John Baldwin <jhb@FreeBSD.org>
To: freebsd-current@FreeBSD.org
Date: Mon, 15 Nov 2004 16:06:45 -0500
User-Agent: KMail/1.6.2
References: <Pine.NEB.3.96L.1041115133457.80435A-100000@fledge.watson.org>
	<200411150857.42423.peter@wemm.org> <20041115180045.B53544@cvs.imp.ch>
In-Reply-To: <20041115180045.B53544@cvs.imp.ch>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200411151606.45640.jhb@FreeBSD.org>
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx
cc: Martin Blapp <mb@imp.ch>
cc: Robert Watson <rwatson@FreeBSD.org>
cc: current@FreeBSD.org
Subject: Re: Deadlock problems with 'kill PID' on CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Nov 2004 21:18:55 -0000

On Monday 15 November 2004 12:03 pm, Martin Blapp wrote:
> Hi,
>
> > I had this problem too BTW, but it didn't prevent DDB.  Once named or
> > rndc got stuck, trying to kill them was Really Bad(TM).  Both use
> > libpthread.  The programs were stuck in "runnable" state according to
> > CTRL-T (siginfo).
> >
> > No, I haven't looked closer.  That system was built about when the last
> > round of libpthread turmoil was happening.
>
> Now if you say it. I had to kill named manually since it has lost his
> ARGV:
>
> Instead of
>
> bind        5068  0.0  1.4 30108 28440  ??  Ss   11:51AM  14:54.01
> /usr/sbin/named -u bind -t /var/named
>
> I just had this at the time the box crashed:
>
> bind        5068  0.0  1.4 30108 28440  ??  Ss   11:51AM  14:54.01
> [/usr/sbin/named]
>
> or
>
> bind        5068  0.0  1.4 30108 28440  ??  Ss   11:51AM  14:54.01 [named]
>
> after recovery from the crash, now everything is ok again.

Was the box swapping at the time?  It could be that named was swapped out when 
you tried to kill it.

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org