From owner-freebsd-current@FreeBSD.ORG Sun Nov 16 11:23:48 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 7F34216A4CF for ; Sun, 16 Nov 2003 11:23:48 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DB2443FAF for ; Sun, 16 Nov 2003 11:23:47 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) hAGJNe8I093576; Sun, 16 Nov 2003 11:23:40 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)hAGJNetW093575; Sun, 16 Nov 2003 11:23:40 -0800 (PST) (envelope-from sgk) Date: Sun, 16 Nov 2003 11:23:40 -0800 From: Steve Kargl To: Francis Ridder Message-ID: <20031116192340.GA93567@troutmask.apl.washington.edu> References: <20031116082719.6EF5316A4CE@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: Non-sleepable locks held. 12 hours old source 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: Sun, 16 Nov 2003 19:23:48 -0000 On Sun, Nov 16, 2003 at 12:50:47PM -0600, Francis Ridder wrote: > Ok, at the tail end of the dmesg file I am getting complaints starting at > boot time of non-sleepable locks held. My source is current as of 12 hours > ago. Pasted here is one of the errors: > > checking stopevent 2 with the following non-sleepable locks held: > exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked @ > /usr/src/sys/kern/kern_condvar.c:289 > checking stopevent 2 with the following non-sleepable locks held: > exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked @ > /usr/src/sys/kern/subr_trap.c:260 > checking stopevent 2 with the following non-sleepable locks held: > exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked @ > /usr/src/sys/kern/subr_trap.c:260 > Re-cvsup and biuld a new kernel. Warner removed the warning message, but the problem still exists. -- Steve