From owner-freebsd-current Fri Jul 2 2:28:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 3448814F42 for ; Fri, 2 Jul 1999 02:28:55 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id LAA27946; Fri, 2 Jul 1999 11:28:39 +0200 (MET DST) Date: Fri, 2 Jul 1999 11:28:37 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Alexander Langer Cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-Reply-To: <19990812100720.B707@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you are still running current, please cvsup the newest sources. This problem has been solved in the past few days. It showed up on saturday evening after a commit on McKusick and most of the problem area's have been identified and tracked down. There might still be one or two remaining, but these should be very infrequent. Nick On Thu, 12 Aug 1999, Alexander Langer wrote: > Thus spake Matthew Jacob (mjacob@feral.com): > > > 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 to get PGP-Key *** > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message