From owner-freebsd-net@FreeBSD.ORG  Mon Apr 14 20:30:10 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2AD6B1065672;
	Mon, 14 Apr 2008 20:30:10 +0000 (UTC) (envelope-from vwe@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 035218FC17;
	Mon, 14 Apr 2008 20:30:10 +0000 (UTC) (envelope-from vwe@FreeBSD.org)
Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m3EKU9Xn031425;
	Mon, 14 Apr 2008 20:30:09 GMT
	(envelope-from vwe@freefall.freebsd.org)
Received: (from vwe@localhost)
	by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m3EKU9vo031419;
	Mon, 14 Apr 2008 20:30:09 GMT (envelope-from vwe)
Date: Mon, 14 Apr 2008 20:30:09 GMT
Message-Id: <200804142030.m3EKU9vo031419@freefall.freebsd.org>
To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org
From: vwe@FreeBSD.org
Cc: 
Subject: Re: kern/122743: [panic] vm_page_unwire: invalid wire count: 0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2008 20:30:10 -0000

Old Synopsis: panic: vm_page_unwire: invalid wire count: 0
New Synopsis: [panic] vm_page_unwire: invalid wire count: 0

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: vwe
Responsible-Changed-When: Mon Apr 14 20:27:51 UTC 2008
Responsible-Changed-Why: 

while this is looking like a vm fault, it seems to be caused by the
network subsystem having a problem in mbuf handling.
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=122743