From owner-freebsd-current@FreeBSD.ORG Fri Jan 23 15:35:19 2004 Return-Path: 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 07F4E16A4CE; Fri, 23 Jan 2004 15:35:19 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id E544043D3F; Fri, 23 Jan 2004 15:35:17 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc12) with ESMTP id <20040123233516012002l4dte>; Fri, 23 Jan 2004 23:35:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA42560; Fri, 23 Jan 2004 15:35:18 -0800 (PST) Date: Fri, 23 Jan 2004 15:35:17 -0800 (PST) From: Julian Elischer To: Ruslan Ermilov In-Reply-To: <20040123191845.GA41158@FreeBSD.org.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Julian Elischer cc: current@FreeBSD.org Subject: Re: blockable sleep lock (sleep mutex) netgraph nodelist mutex panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 23:35:19 -0000 hmmmmmm ok.. I guess I need to investigate if I need loop detection.. thanks On Fri, 23 Jan 2004, Ruslan Ermilov wrote: > 5.2-CURRENT. Connecting a Netgraph node to itself results in the > following panic on the node shutdown: > > : blockable sleep lock (sleep mutex) netgraph nodelist mutex @ /usr/src/sys/netgraph/ng_base.c:952 > > To reproduce, just type: ``ngctl connect . . foo bar''. This will > panic instantly. > > > Cheers, > -- > Ruslan Ermilov > FreeBSD committer > ru@FreeBSD.org >