From owner-freebsd-bugs@FreeBSD.ORG  Fri Jan 13 01:30:14 2006
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4C67D16A41F
	for <freebsd-bugs@hub.freebsd.org>;
	Fri, 13 Jan 2006 01:30:14 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9CE3943D45
	for <freebsd-bugs@hub.freebsd.org>;
	Fri, 13 Jan 2006 01:30:13 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0D1UDcB036948
	for <freebsd-bugs@freefall.freebsd.org>; Fri, 13 Jan 2006 01:30:13 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k0D1UDJX036947;
	Fri, 13 Jan 2006 01:30:13 GMT (envelope-from gnats)
Date: Fri, 13 Jan 2006 01:30:13 GMT
Message-Id: <200601130130.k0D1UDJX036947@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Robert Huff <roberthuff@rcn.com>
Cc: 
Subject: Re: kern/86427: LOR / Deadlock with FASTIPSEC and nat
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Robert Huff <roberthuff@rcn.com>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jan 2006 01:30:14 -0000

The following reply was made to PR kern/86427; it has been noted by GNATS.

From: Robert Huff <roberthuff@rcn.com>
To: bug-followup@FreeBSD.org,  mike@sentex.net
Cc:  
Subject: Re: kern/86427: LOR / Deadlock with FASTIPSEC and nat
Date: Thu, 12 Jan 2006 20:23:11 -0500

 	I'm getting what seems to be either the same problem or its fraternal 
 twin ... only without either IPSEC (any flavor) or any vpn.
 	Running
 
 FreeBSD 7.0-CURRENT #0: Wed Jan  4 13:41:21 EST 20
 
 	I get this
 
 Jan 12 19:27:51 jerusalem kernel: lock order reversal:
 Jan 12 19:27:51 jerusalem kernel: 1st 0xc364a090 inp (divinp) @ 
 /usr/src/sys/netinet/ip_divert.c:327
 Jan 12 19:27:51 jerusalem kernel: 2nd 0xc07655cc in_multi_mtx 
 (in_multi_mtx) @ /usr/src/sys/netinet/ip_output.c:291
 Jan 12 19:27:51 jerusalem kernel: KDB: stack backtrace:
 Jan 12 19:27:51 jerusalem kernel: 
 kdb_backtrace(c06b7a91,c07655cc,c06b7470,c06b7470,c06c0886) at 
 kdb_backtrace+0x2f
 Jan 12 19:27:51 jerusalem kernel: 
 witness_checkorder(c07655cc,9,c06c0886,123,c06bead6) at 
 witness_checkorder+0x6e1
 Jan 12 19:27:51 jerusalem kernel: 
 _mtx_lock_flags(c07655cc,0,c06c0886,123,c05427bd) at _mtx_lock_flags+0x85
 Jan 12 19:27:51 jerusalem kernel: ip_output(c33c0b00,0,d56e5afc,22,0) 
 at ip_output+0x460
 Jan 12 19:27:51 jerusalem kernel: 
 div_output(c35ff000,c33c0b00,c341d970,0,d56e5bb8) at div_output+0x1d5
 Jan 12 19:27:51 jerusalem kernel: 
 div_send(c35ff000,0,c33c0b00,c341d970,0) at div_send+0x5d
 Jan 12 19:27:51 jerusalem kernel: 
 sosend(c35ff000,c341d970,d56e5be4,c33c0b00,0) at sosend+0x49e
 Jan 12 19:27:51 jerusalem kernel: kern_sendit(c339c900,3,d56e5c64,0,0) 
 at kern_sendit+0x106
 Jan 12 19:27:51 jerusalem kernel: 
 sendit(c339c900,3,d56e5c64,0,bfbeedb0) at sendit+0x1a8
 Jan 12 19:27:51 jerusalem kernel: sendto(c339c900,d56e5d04,18,43c,6) 
 at sendto+0x5b
 Jan 12 19:27:51 jerusalem kernel: syscall(3b,3b,3b,bfbeed90,2) at 
 syscall+0x2a6
 Jan 12 19:27:51 jerusalem kernel: Xint0x80_syscall() at 
 Xint0x80_syscall+0x1f
 Jan 12 19:27:51 jerusalem kernel: --- syscall (133, FreeBSD ELF32, 
 sendto), eip
 
 	and startup continues.
 	If this is a problem with ipfw, it's one that happened since 
 approximately the middle of December.