Date: Tue, 11 Mar 2003 18:59:15 -0600 (CST) From: Jonathan Lemon <jlemon@flugsvamp.com> To: dlt@mebtel.net, current@freebsd.org Subject: Re: exclusive sleep mutex netisr... Message-ID: <200303120059.h2C0xFdt092736@mail.flugsvamp.com> In-Reply-To: <local.mail.freebsd-current/20030311231140.GA3881@mebtel.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-current/20030311231140.GA3881@mebtel.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303120059.h2C0xFdt092736>