From owner-freebsd-current Mon May 21 1:20:39 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 F21E537B422; Mon, 21 May 2001 01:20:34 -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:20:33 +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 "Sun, 20 May 2001 13:29:22 PDT." <20010520202933.847EB3E0B@bazooka.unixfreak.org> X-Request-Do: Date: Mon, 21 May 2001 09:20:31 +0100 From: David Malone Message-ID: <200105210920.aa71413@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 > Please try the attached patch. I make no claims of its correctness, > but this e-mail is coming to you via X on -current updated a few hours > ago so it works here :-). 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: panic+0x70 _mtx_assert+0x67 lockmgr+0xdc vm_map_remove+0x42 shm_delete_mapping+0xe1 shmexit_myhook+0x29 exit1+0x9eb exit1 So it looks like those routines are sometime called with the mutex already held. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message