From owner-freebsd-current  Sun Jun 27  9: 3:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP
	id 66D1314D4F; Sun, 27 Jun 1999 08:57:08 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 9DBCB81; Sun, 27 Jun 1999 23:56:46 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Seigo Tanimura <tanimura@naklab.dnj.ynu.ac.jp>
Cc: hibma@skylink.it, current@FreeBSD.ORG, mckusick@FreeBSD.ORG
Subject: Re: lockmgr panics 
In-reply-to: Your message of "Mon, 28 Jun 1999 00:49:21 +0900."
             <19990628004921U.tanimura@sakuramail.com> 
Date: Sun, 27 Jun 1999 23:56:46 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990627155646.9DBCB81@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Seigo Tanimura wrote:
> From: Nick Hibma <hibma@skylink.it>
> Subject: lockmgr panics
> Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST)
> Message-ID: <Pine.BSF.3.96.990627140352.2769A-100000@heidi.plazza.it>
> 
> hibma> lockmgr: pid <some pid>, not exclusive lock holder -2 unlocking
> 
> 
> Did you really get that message? if the unlocking process is
> pid -2(LK_KERNPROC), we can unlock, as in:
> 
> [sys/kern/kern_lock.c:lockmgr()]
> >         case LK_RELEASE:
> >                 if (lkp->lk_exclusivecount != 0) {
> > #if !defined(MAX_PERF)
> >                         if (lkp->lk_lockholder != pid &&
> >                             lkp->lk_lockholder != LK_KERNPROC) /* FALSE */
> >                                 panic("lockmgr: pid %d, not %s %d unlocking
    ",
> >                                     pid, "exclusive lock holder",
> >                                     lkp->lk_lockholder);
> 
> Although the fixes by Peter seemed to have solved the problem, I saw
> 
> lockmgr: pid -2, not exclusive lock holder 48 unlocking
>
> on savecore(8) after another panic reboot.

I've had that too, also from savecore...

Cheers,
-Peter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message