From owner-freebsd-current@FreeBSD.ORG  Mon Nov 15 17:03:58 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 3A0C816A4D0; Mon, 15 Nov 2004 17:03:58 +0000 (GMT)
Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id CEB1743D41; Mon, 15 Nov 2004 17:03:55 +0000 (GMT)
	(envelope-from mb@imp.ch)
Received: from mx2.imp.ch (mx2o [157.161.9.17])
	by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id iAFH3hx2058287;
	Mon, 15 Nov 2004 18:03:44 +0100 (CET)
	(envelope-from mb@imp.ch)
Received: from mx2.imp.ch (localhost [127.0.0.1])
	by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id iAFH3eLi067374;
	Mon, 15 Nov 2004 18:03:41 +0100 (CET)
	(envelope-from mb@imp.ch)
Received: (from clamav@localhost)
	by mx2.imp.ch (8.12.11/8.12.11/Submit) id iAFH3eJG067371;
	Mon, 15 Nov 2004 18:03:40 +0100 (CET)
	(envelope-from mb@imp.ch)
X-Authentication-Warning: mx2.imp.ch: clamav set sender to <mb@imp.ch> using
	-f
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by ns1.imp.ch (MIMEDefang) with ESMTP id iAFH3aXY045890;
	Mon, 15 Nov 2004 18:03:40 +0100 (CET)
Date: Mon, 15 Nov 2004 18:03:36 +0100 (CET)
From: Martin Blapp <mb@imp.ch>
To: Peter Wemm <peter@wemm.org>
In-Reply-To: <200411150857.42423.peter@wemm.org>
Message-ID: <20041115180045.B53544@cvs.imp.ch>
References: <Pine.NEB.3.96L.1041115133457.80435A-100000@fledge.watson.org>
 <200411150857.42423.peter@wemm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Resent: Yes
X-Spam-Checksum: 746e0eaaf5076b0e7c5f49d4b0befca1
X-Virus-Message-Status: No
X-Virus-Status: No, scantime="0.0018 seconds"
X-Spam-Status: No, hits=-4.9 required=5 scantime="5.9418 seconds"
	tests=BAYES_00
X-Scanned-By: MIMEDefang 2.48 on 157.161.9.18
cc: freebsd-current@freebsd.org
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 17:03:58 -0000


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.

Martin