From owner-freebsd-smp Sun Jan 20 11:52:52 2002 Delivered-To: freebsd-smp@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8EFA037B484 for ; Sun, 20 Jan 2002 11:52:40 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g0KJqY086603; Sun, 20 Jan 2002 11:52:34 -0800 (PST) (envelope-from dillon) Date: Sun, 20 Jan 2002 11:52:34 -0800 (PST) From: Matthew Dillon Message-Id: <200201201952.g0KJqY086603@apollo.backplane.com> To: Alfred Perlstein Cc: Terry Lambert , smp@FreeBSD.ORG Subject: Re: help with mutex_pool please? References: <20020119080125.X13686@elvis.mu.org> <3C4A4362.8A98209D@mindspring.com> <20020120032757.B13686@elvis.mu.org> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org : :* Terry Lambert [020119 20:11] wrote: :> Alfred Perlstein wrote: :> > :> > I was going to convert some subsystems to use mutex pools... :> > :> > However if I apply this delta, a couple of seconds after boot I get :> > a lockup, sometimes the panic message is printed "sleeping with :> > mutex held" :> > :> > Any clues? :> :> Implied unlock on the two destroys you removed? : :Ah, thanks! : :-- :-Alfred Perlstein [alfred@freebsd.org] That sounds like a misfeature, since there had better not be any contention with another process anyway when a mutex is in the process of being destroyed. The mutex destroy function should probably panic when it finds the mutex held and we should fix whatever other cases use the misfeature. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message