From owner-freebsd-current Tue Mar 11 16:59:55 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 D226837B401 for ; Tue, 11 Mar 2003 16:59:53 -0800 (PST) Received: from mail.flugsvamp.com (ts46-01-qdr3643.mdfrd.or.charter.com [68.118.36.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9188343FBF for ; Tue, 11 Mar 2003 16:59:52 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by mail.flugsvamp.com (8.12.6/8.12.6) id h2C0xFdt092736; Tue, 11 Mar 2003 18:59:15 -0600 (CST) (envelope-from jlemon) 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... X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: 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 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