From owner-freebsd-current Tue Mar 11 17:28: 8 2003 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 97AAB37B401 for ; Tue, 11 Mar 2003 17:28:06 -0800 (PST) Received: from mailrelay.mebtel.net (spambuster4.mebtel.net [64.40.67.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2F1A43F93 for ; Tue, 11 Mar 2003 17:28:05 -0800 (PST) (envelope-from dlt@mebtel.net) Received: from lorne.arm.org (64-40-71-66.dsl.mebtel.net [64.40.71.66]) by mailrelay.mebtel.net (Postfix) with ESMTP id 9C284276DA; Tue, 11 Mar 2003 20:22:33 -0500 (EST) Received: from lorne.arm.org (localhost [127.0.0.1]) by lorne.arm.org (8.12.8/8.12.8) with ESMTP id h2C1S40M004295; Tue, 11 Mar 2003 20:28:04 -0500 (EST) (envelope-from dlt@lorne.arm.org) Received: (from dlt@localhost) by lorne.arm.org (8.12.8/8.12.8/Submit) id h2C1S4LF004294; Tue, 11 Mar 2003 20:28:04 -0500 (EST) Date: Tue, 11 Mar 2003 20:28:03 -0500 From: Derek Tattersall To: Jonathan Lemon Cc: current@freebsd.org Subject: Re: exclusive sleep mutex netisr... Message-ID: <20030312012803.GA4243@mebtel.net> Reply-To: dlt@mebtel.net References: <200303120059.h2C0xFdt092736@mail.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200303120059.h2C0xFdt092736@mail.flugsvamp.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Jonathan Lemon (jlemon@flugsvamp.com) [030312 01:12]: > Date: Tue, 11 Mar 2003 18:59:15 -0600 (CST) > From: Jonathan Lemon > Message-Id: <200303120059.h2C0xFdt092736@mail.flugsvamp.com> > To: dlt@mebtel.net, current@freebsd.org > Subject: Re: exclusive sleep mutex netisr... > Organization: > Cc: > > In article you write: > >I see several instances of this in /var/log/messages after cvsup'ing > >Monday evening and rebuilding world and kernel. I haven't seen any > >messages about this, so I figured I'd ask here. > > > >Message: > >Mar 11 17:33:30 lorne kernel: malloc() of "64" with the following > >non-sleepablelocks held: > >Mar 11 17:33:30 lorne kernel: exclusive sleep mutex netisr lock r = 0 > >(0xc0579160) locked @ /usr/src/sys/net/netisr.c:215 > > > >Can anybody supply me a clue as to what's going on here? > > It can be ignored for now, the code path is still under the Giant lock, > so this is harmless, I'll fix this soon to use a different approach; > the lock was intended to protect against reentrancy. > > However, I'd be interested to know what is calling malloc(), if that > information is in the syslog. > -- > Jonathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > The only other bit of information I have is: Mar 10 20:55:09 lorne kernel: Bad malloc flags: 4 Mar 10 20:55:09 lorne kernel: Stack backtrace: Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following non-sleepablelocks held: Mar 10 20:55:09 lorne kernel: exclusive sleep mutex netisr lock r = 0 (0xc0579160) locked @ /usr/src/sys/net/netisr.c:215 Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following non-sleepablelocks held: Mar 10 20:55:09 lorne kernel: exclusive sleep mutex netisr lock r = 0 (0xc0579160) locked @ /usr/src/sys/net/netisr.c:215 I haven't found anything that was crisper. I hope this is useful. I'll keep following the list for more info. -- Derek Tattersall dlt@mebtel.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message