From owner-freebsd-current Wed Mar 12 7:48:58 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 0EFF437B401 for ; Wed, 12 Mar 2003 07:48:56 -0800 (PST) Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E3843F75 for ; Wed, 12 Mar 2003 07:48:55 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 932 invoked from network); 12 Mar 2003 15:48:57 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Mar 2003 15:48:57 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id h2CFivhT038287; Wed, 12 Mar 2003 10:44:57 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030312012803.GA4243@mebtel.net> Date: Wed, 12 Mar 2003 10:49:09 -0500 (EST) From: John Baldwin To: Derek Tattersall Subject: Re: exclusive sleep mutex netisr... Cc: current@freebsd.org, Jonathan Lemon 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 On 12-Mar-2003 Derek Tattersall wrote: > * 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. You can turn on witness_ddb and get a stack trace to see where malloc() is called from. You might also be able to use witness_trace to do this. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message