Date: Mon, 28 Jun 1999 00:49:21 +0900 From: Seigo Tanimura <tanimura@naklab.dnj.ynu.ac.jp> To: hibma@skylink.it Cc: Seigo Tanimura <tanimura@naklab.dnj.ynu.ac.jp> Subject: Re: lockmgr panics Message-ID: <19990628004921U.tanimura@sakuramail.com> In-Reply-To: Your message of "Sun, 27 Jun 1999 14:15:06 %2B0200 (CEST)" <Pine.BSF.3.96.990627140352.2769A-100000@heidi.plazza.it> References: <Pine.BSF.3.96.990627140352.2769A-100000@heidi.plazza.it>
next in thread | previous in thread | raw e-mail | index | archive | help
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 have to go to bed now... I will see what is going on tomorrow.
Seigo TANIMURA <tanimura@naklab.dnj.ynu.ac.jp>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990628004921U.tanimura>