I got this a few days ago. Apparently there was some form of problem
with the vm subsystem (I'm speculating here). What I did to fix it was
to re-cvsup the source tree (after killing non-essential processes) and
rebuilding only the kernel. After compiling and installing the new
kernel, I rebooted and reran a full make world. Everything seems to be
working well, now.
Jerry
Alexander Langer wrote:
>
> Thus spake Matthew Jacob ([EMAIL PROTECTED]):
>
> > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
>
> I got this very often the last days, too.
>
> Actually I try do downgrade to 3.2, because my machines reboots 3
> times a day because of either this error or other things. -CURRENT
> actually is VERY unstable here.
>
> Alex
> --
> ************** I doubt, therefore I might be. **************
> *** Send email to <[EMAIL PROTECTED]> to get PGP-Key ***
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
