From owner-freebsd-current@FreeBSD.ORG  Wed Apr  2 15:18:38 2003
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 05F8B37B404
	for <current@freebsd.org>; Wed,  2 Apr 2003 15:18:38 -0800 (PST)
Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5058043FB1
	for <current@freebsd.org>; Wed,  2 Apr 2003 15:18:37 -0800 (PST)
	(envelope-from jroberson@chesapeake.net)
Received: from localhost (jroberson@localhost)
	by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32NIWH77574;
	Wed, 2 Apr 2003 18:18:32 -0500 (EST)
	(envelope-from jroberson@chesapeake.net)
Date: Wed, 2 Apr 2003 18:18:32 -0500 (EST)
From: Jeff Roberson <jroberson@chesapeake.net>
To: Gordon Tetlow <gordont@gnf.org>
In-Reply-To: <20030402231345.GF69100@roark.gnf.org>
Message-ID: <20030402181809.O64602-100000@mail.chesapeake.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: LOR on libthr exit (iirc)
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: Wed, 02 Apr 2003 23:18:38 -0000


On Wed, 2 Apr 2003, Gordon Tetlow wrote:

> I think it was a libthr linked app after I killed it:

Yeah, this is a problem with the thread single exit and suspend code.  I
haven't fixed it yet.  Thanks for the report.

> lock order reversal
>  1st 0xc679d248 process lock (process lock) @ /local/usr.src/sys/kern/kern_exit.
> c:134
>  2nd 0xc05394a0 Giant (Giant) @ /local/usr.src/sys/kern/kern_exit.c:142
> Stack backtrace:
> backtrace(c04e759f,c05394a0,c04e3f7f,c04e3f7f,c04e2359) at backtrace+0x17
> witness_lock(c05394a0,8,c04e2359,8e,0) at witness_lock+0x692
> _mtx_lock_flags(c05394a0,0,c04e2359,8e,c6d9deac) at _mtx_lock_flags+0xb2
> exit1(c6d9de40,f00,c04e2359,63,e9971d40) at exit1+0x174
> sys_exit(c6d9de40,e9971d14,c04ff422,404,1) at sys_exit+0x41
> syscall(2f,2f,2f,0,ffffffff) at syscall+0x24e
> Xint0x80_syscall() at Xint0x80_syscall+0x1d
> --- syscall (1), eip = 0x280ef90f, esp = 0xbf91071c, ebp = 0xbf910738 ---
>
> -gordon
>