From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 18:28:38 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 863DD16A4CE for ; Wed, 17 Nov 2004 18:28:38 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 709FB43D58 for ; Wed, 17 Nov 2004 18:28:38 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4761272DD4; Wed, 17 Nov 2004 10:28:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 4585172DCB; Wed, 17 Nov 2004 10:28:38 -0800 (PST) Date: Wed, 17 Nov 2004 10:28:38 -0800 (PST) From: Doug White To: Sean McNeil In-Reply-To: <1100657472.74795.2.camel@server.mcneil.com> Message-ID: <20041117102623.P25028@carver.gumbysoft.com> References: <1100657472.74795.2.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? 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: Wed, 17 Nov 2004 18:28:38 -0000 On Tue, 16 Nov 2004, Sean McNeil wrote: > This has been happening for a long time with current and hasn't been > resolved. When I start up slapd, I cannot stop it without kill -9 ing > it. It would appear stuck in kse and probably has something to do with > kill -0: Mind expanding on this? The backtrace looks normal for a pthread process. kill -0 just tests signal delivery; the process is completely unaware that the probe occured, though. The process may also be unkillable if its stuck in some sort of I/O wait. Is the server busy when you signal it? > > (gdb) bt > #0 0x000000080142e914 in kse_release () at kse_release.S:2 > #1 0x0000000801428e49 in kse_wait (kse=0x62a000, td_wait=0x0, > sigseqno=0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1843 > #2 0x0000000801427078 in kse_sched_multi (kmbx=0x62efa0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1039 > #3 0x000000080142afbf in _amd64_enter_uts () > at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 > #4 0x0000000000000000 in ?? () > #5 0x000000000062f000 in ?? () > #6 0x000000000062a000 in ?? () > #7 0x0000000000000000 in ?? () > #8 0x0000000000000000 in ?? () > #9 0x0000000000000000 in ?? () > #10 0x0000000000000000 in ?? () > #11 0x0000000000000000 in ?? () > #12 0x0000000000000001 in ?? () > #13 0x0000000801426dd0 in _thr_sched_switch_unlocked () > at /usr/src/lib/libpthread/thread/thr_kern.c:904 > Previous frame inner to this frame (corrupt stack?) > > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org