From owner-freebsd-current Fri Jul 28 14:17:33 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 4D93837B651; Fri, 28 Jul 2000 14:17:31 -0700 (PDT) Date: Fri, 28 Jul 2000 14:17:31 -0700 From: "Andrey A. Chernov" To: Scott Flatman Cc: Brian Fundakowski Feldman , Sheldon Hearn , Kirk McKusick , current@FreeBSD.ORG Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000728141728.A44135@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from sf@aracnet.com on Fri, Jul 28, 2000 at 11:36:26AM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 28, 2000 at 11:36:26AM -0700, Scott Flatman wrote: > On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > > > I havne't been able to reproduce this, but this case is going to have > > more to do with analysis of the code than with "debugging", I think. > > By chance are you running with softupdates enabled on /? If I can > > reproduce it here, I will spend a while inspecting all the state to > > figure this one out as best as possible. > > I get the same panic 100% of the time upon reboot. So I can quite > easily reproduce it. :) I too. The only way I can avoid this panic is 1) Remove /erc/rc.shutdown (which write files) 2) Do several syns manually before reboot. In all other situations I got this panic. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message