From owner-freebsd-current@FreeBSD.ORG Fri Jan 16 13:48:28 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 D040D16A4DB for ; Fri, 16 Jan 2004 13:48:28 -0800 (PST) Received: from odot.okladot.state.ok.us (odot.okladot.state.ok.us [192.149.244.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5045943D45 for ; Fri, 16 Jan 2004 13:48:27 -0800 (PST) (envelope-from root@techpc04.okladot.state.ok.us) Received: from notes9c.okladot.state.ok.us (notes9a.okladot.state.ok.us [10.36.36.31])PAA51164; Fri, 16 Jan 2004 15:48:26 -0600 Received: from techpc04.okladot.state.ok.us ([199.27.9.37]) by notes9c.okladot.state.ok.us (Lotus Domino Release 5.0.12) with ESMTP id 2004011615490134:431968 ; Fri, 16 Jan 2004 15:49:01 -0600 Received: by techpc04.okladot.state.ok.us (Postfix, from userid 0) id 05D6E5C3A; Fri, 16 Jan 2004 15:48:25 -0600 (CST) To: freebsd-current@freebsd.org From: pdseniura@techie.com Message-Id: <20040116214825.05D6E5C3A@techpc04.okladot.state.ok.us> Date: Fri, 16 Jan 2004 15:48:25 -0600 (CST) X-MIMETrack: Itemize by SMTP Server on Notes9c/ODOT(Release 5.0.12 |February 13, 2003) at 01/16/2004 03:49:01 PM,2003) at 01/16/2004 03:49:02 PM, Serialize complete at 01/16/2004 03:49:02 PM X-Mailman-Approved-At: Fri, 16 Jan 2004 14:54:16 -0800 cc: pdseniura@techie.com Subject: non-sleepable locks in kern_fork.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pdseniura@techie.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 21:48:29 -0000 I'm seeing this way WAY too many times as of last night's CTM deltas (Central Standard Time): malloc() of "256" with the following non-sleepable locks held: exclusive sleep mutex filedesc structure r = 0 (0xc3a54a38) locked @ /src/sys/kern/kern_fork.c:421 I built+installed world & kernel etc. as usual. I'm pressed for time right now; I'll need to go back to the previous kernel and continue looking at this on Monday. Maybe by then s'more patches will come out to fix it. ;) (I use MacOSX at home, no li'l-endian machines there at all ;) Thanks, -- Paul Seniura System Specialist State of Okla. D.O.T.