From owner-freebsd-current Mon May 21 1:53:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 762B637B422; Mon, 21 May 2001 01:53:24 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 May 2001 09:53:23 +0100 (BST) To: Dima Dorfman Cc: mheffner@vt.edu, freebsd-current@freebsd.org, alfred@freebsd.org Subject: Re: panic: mutex vm not owned In-reply-to: Your message of "Mon, 21 May 2001 01:44:16 PDT." <20010521084416.6E9763E28@bazooka.unixfreak.org> X-Request-Do: Date: Mon, 21 May 2001 09:53:23 +0100 From: David Malone Message-ID: <200105210953.aa74722@salmon.maths.tcd.ie> 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 > > I tried Dima's patch (the one which Alfred has committed) and I > > get an earlier mutex recursion panic, probably when a local progam > > that uses shm forks and exits. I scribbled down this trace from > > it: > Is there such a program in the base system? Nope - it's part of a radio refclock for NTP. It doesn't do anything magic though - just shares a shm segement with ntpd and gets times from the serial port. > Attached is an untested patch to try to fix this. It's almost 02:00 > here and I have to head to bed, but it may work for you. At least it > may be a starting point for someone. I won't be able to apply the patch until I get home from work. Should I apply it on top of the other patch? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message