From owner-freebsd-current@FreeBSD.ORG  Wed Dec 29 11:36:42 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 9942E16A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 29 Dec 2004 11:36:42 +0000 (GMT)
Received: from mx.laposte.net (mx.laposte.net [80.245.62.11])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A68ED43D5C
	for <freebsd-current@freebsd.org>;
	Wed, 29 Dec 2004 11:36:41 +0000 (GMT)
	(envelope-from antoine.brodin@laposte.net)
Received: from localhost (82.67.196.50) by mx.laposte.net (7.0.028)
	(authenticated as antoine.brodin@laposte.net)
	id 41B63F920078BEFF for freebsd-current@freebsd.org;
	Wed, 29 Dec 2004 12:36:40 +0100
Date: Wed, 29 Dec 2004 12:36:40 +0100
From: Antoine Brodin <antoine.brodin@laposte.net>
To: freebsd-current@freebsd.org
Message-Id: <20041229123640.449339e1.antoine.brodin@laposte.net>
X-Mailer: Sylpheed version 1.0.0rc (GTK+ 1.2.10; i386-portbld-freebsd6.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: acquiring duplicate lock of same type: "network driver"
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, 29 Dec 2004 11:36:42 -0000

Hi,

Witness reports this on a recent -current box (2 days old) doing nat
with pf :

acquiring duplicate lock of same type: "network driver"
 1st nv0 @ /usr/ports/net/nvnet/work/nvnet/module/../src/if_nv.c:1511
 2nd skc0 @ /usr/src/sys/modules/sk/../../pci/if_sk.c:1112
KDB: stack backtrace:
witness_checkorder(c2855c44,9,c07316ba,458) at witness_checkorder+0x500
_mtx_lock_flags(c2855c44,0,c07316ba,458,c2ac4e00) at _mtx_lock_flags+0x40
sk_jfree(e5a44340,c28e3000,0,c2857c00,e3c79c80) at sk_jfree+0x33
mb_free_ext(c2ac4e00) at mb_free_ext+0x36
m_freem(c2ac4e00,c2857c00,e5901000,e56fb0e0,c2857e60) at m_freem+0x21
nv_ospackettx(c2857c00,e56fb0e0,1,e5901000,0) at nv_ospackettx+0x73
UpdateTransmitDescRingData() at UpdateTransmitDescRingData+0xd3

(it probably happened before but I didn't have witness enabled)
This could perhaps deadlock a box with 2 sk(4) interfaces...

Cheers,

Antoine