Seigo Tanimura wrote:
> From: Nick Hibma <[EMAIL PROTECTED]>
> Subject: lockmgr panics
> Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST)
> Message-ID: <[EMAIL PROTECTED]>
>
> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
