From owner-freebsd-current@FreeBSD.ORG Tue Nov 11 15:53:52 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 2A9A016A4CE for ; Tue, 11 Nov 2003 15:53:52 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22A1D43F75 for ; Tue, 11 Nov 2003 15:53:51 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hABNq3Mg079408; Tue, 11 Nov 2003 18:52:03 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hABNq3Ad079405; Tue, 11 Nov 2003 18:52:03 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 11 Nov 2003 18:52:03 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: cosmin In-Reply-To: <20031111225646.GA5506@nacom.phy.uic.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: NFS problem (non-sleepable locks held) 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: Tue, 11 Nov 2003 23:53:52 -0000 On Tue, 11 Nov 2003, cosmin wrote: > I'm getting the following message when transfering data to a > freebsd-current server via an nfs mount from another fbsd client. > > malloc() of "64" with the following non-sleepable locks held: exclusive > sleep mutex inp r = 0 (0xc1d250ac) locked @ > /usr/src/sys/netinet/udp_usrreq.c:378 > > The message shows up 12 times and then it doesn't show up anymore, even > if I stop the transfer and start it again. This server uses the nge > driver for its network card. It's running the sources from yesterday, > Nov 10 2003. > > I've been having problems with one of our machines freezing up during > long nfs transfers, and now i'm trying to reproduce the freeze on this > test machine. So far no luck, and the only oddity i've been getting is > the above message. > > Could the above message be causing the freezes ? Could you hook up a serial console and turn on debug.witness_ddb. When you get this warning, you'll drop into the console debugger. Type in "trace" to get a stack trace. You can then continue and turn it off again (or drop into the debugger a few more times until you're able to run it :-). Basically, something is calling malloc with M_WAITOK while holding a mutex. Potentially this could cause stalls or resource deadlocks, but I think it's likely not the source of your freezes. On the other hand, it's definitely worth fixing, and if it fixes the symptoms you're seeing, even better :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories