From owner-freebsd-current@FreeBSD.ORG Sat Jun 21 06:44:24 2003 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 E7CA637B401; Sat, 21 Jun 2003 06:44:24 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B51043F3F; Sat, 21 Jun 2003 06:44:24 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfi5h.dialup.mindspring.com ([165.247.200.177] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19TifH-0007fb-00; Sat, 21 Jun 2003 06:44:24 -0700 Message-ID: <3EF460E5.86A45983@mindspring.com> Date: Sat, 21 Jun 2003 06:43:01 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Hiten Pandya References: <20030619221703.GD64061@funkthat.com> <20030621120809.GC5692@perrin.int.nxad.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4e38481dd0b012f31d3d3fa68c89af35ca7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c cc: freebsd-net@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: locking problems in IPv6 code 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: Sat, 21 Jun 2003 13:44:25 -0000 Hiten Pandya wrote: > On Thu, Jun 19, 2003 at 03:17:03PM -0700, John-Mark Gurney wrote: > > I am running FreeBSD 5.1-R on a sparc64 machine, and am getting warnings > > about mallocing data w/ a lock aquired. > > > > dmesg output: > > malloc() of "64" with the following non-sleepablelocks held: > > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked @ net/netisr.c:215 > > For what it's worth, these warnings also appear if netisr direct > dispatch is enabled with the fxp(4) driver. There are basically 2 structures of exactly 64 bytes in the kernel; one is the zombie structure, and the other is the template structure for TCP. I'm going to guess that this one is the template structure, if you are interested in tracking down the problem. -- Terry