From owner-freebsd-current  Sat May 23 08:12:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA28134
          for freebsd-current-outgoing; Sat, 23 May 1998 08:12:41 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28128
          for <freebsd-current@FreeBSD.ORG>; Sat, 23 May 1998 08:12:37 -0700 (PDT)
          (envelope-from michaelh@cet.co.jp)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id PAA01789; Sat, 23 May 1998 15:11:36 GMT
Date: Sun, 24 May 1998 00:11:36 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Julian Elischer <julian@whistle.com>
cc: The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG
Subject: Re: May 17th UP machine 'panic'
In-Reply-To: <Pine.BSF.3.95.980523000855.24959B-100000@current1.whistle.com>
Message-ID: <Pine.SV4.3.95.980523233045.1499B-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The panic is saying that proc 26748 is trying to unlock an exclusive lock
owned by proc 1.  It doesn't seem to be as you describe.  This might not
have anything to do with quotas at all.  Is vfs_unmountall() in the trace?

Regards,


Mike Hancock

On Sat, 23 May 1998, Julian Elischer wrote:

> you have quotas right?
> the addition of the locking intot he kernel was done without taking into
> account quotas and when winding up the quota file it locks it and then
> tries to lock and release all open files.
> then when it gets to teh quota file..
> oops it's already locked....
> panic ..
> 
> I have no fix yet but I see this  here and am planning on tracking it down
> this weekend.
> 
> 
> On Fri, 22 May 1998, The Hermit Hacker wrote:
> 
> > 
> > On a reboot, I get:
> > 
> > syncing disks... 68 51 25 done
> > panic: lockmgr: pid 26748, not exclusive lock holder 1 unlocking
> > 
> > When I reported this the first time through, the comment had to do with
> > multiple CPUs...except this is a UP motherboard...
> > 
> > Does anyone know why I would be getting this, or if there has been a fix
> > for it in the past 5 days that I haven't clued into on the commit list?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message