From owner-freebsd-current  Tue Aug 26 12:35:57 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA02351
          for current-outgoing; Tue, 26 Aug 1997 12:35:57 -0700 (PDT)
Received: from brane.digs.iafrica.com (brane.digs.iafrica.com [196.7.162.25])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA02336
          for <current@freebsd.org>; Tue, 26 Aug 1997 12:35:36 -0700 (PDT)
Received: from iang by brane.digs.iafrica.com with local (Exim 1.62 #2)
	id 0x3ROB-00019i-00; Tue, 26 Aug 1997 21:34:55 +0200
Subject: Re: lockmgr panic on reboot?
In-Reply-To: <m0x3MB3-000BulC@deadline.snafu.de> from "Andreas S. Wetzel" at "Aug 26, 97 04:01:01 pm"
To: root@deadline.snafu.de (Andreas S. Wetzel)
Date: Tue, 26 Aug 1997 21:34:55 +0200 (SAT)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E0x3ROB-00019i-00@brane.digs.iafrica.com>
From: Ian Freislich <iang@digs.iafrica.com>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I just updated my 486 machine with a recent -current kernel as of
> 08/15/97 and discover a panic on reboot stating that a process is not
> exclusive holder of a lock. Same thing happens with -current kernel as
> of today.

You may have noticed that the PID the panic was complaining about
was in fact the shutdown or reboot pid. It seems to have gone away
with today's kernel though. That means that in the two reboots
(because my PC travels a lot) today, I didn't get that panic.

-- igf (Ian Freislich)