From owner-freebsd-bugs@FreeBSD.ORG  Mon Aug 30 20:52:56 2004
Return-Path: <owner-freebsd-bugs@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 D541D16A4CE; Mon, 30 Aug 2004 20:52:56 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B26C343D4C; Mon, 30 Aug 2004 20:52:56 +0000 (GMT)
	(envelope-from arved@FreeBSD.org)
Received: from freefall.freebsd.org (arved@localhost [127.0.0.1])
	i7UKqu2U011897;	Mon, 30 Aug 2004 20:52:56 GMT
	(envelope-from arved@freefall.freebsd.org)
Received: (from arved@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7UKqu4h011893;
	Mon, 30 Aug 2004 20:52:56 GMT
	(envelope-from arved)
Date: Mon, 30 Aug 2004 20:52:56 GMT
From: Tilman Linneweh <arved@FreeBSD.org>
Message-Id: <200408302052.i7UKqu4h011893@freefall.freebsd.org>
To: nms@otdel-1.org, arved@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/68323: (WITNESS report): malloc(M_WAITOK) of "Mbuf",
	forcing M_NOWAIT with the non-sleepable locks held
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Mon, 30 Aug 2004 20:52:57 -0000

Synopsis: (WITNESS report): malloc(M_WAITOK) of "Mbuf", forcing M_NOWAIT with the non-sleepable locks held

State-Changed-From-To: open->feedback
State-Changed-By: arved
State-Changed-When: Mon Aug 30 20:51:40 GMT 2004
State-Changed-Why: 
Does still happen with a recent CURRENT?

Problems with CURRENT should be reported on the freebsd-current
mailinglist first.

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