From bob@luke.pmr.com  Sat Sep  7 09:23:35 1996
Received: from luke.pmr.com (luke.pmr.com [206.224.65.132])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA15922
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 7 Sep 1996 09:23:34 -0700 (PDT)
Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.7.3) id LAA17872; Sat, 7 Sep 1996 11:23:28 -0500 (CDT)
Message-Id: <199609071623.LAA17872@luke.pmr.com>
Date: Sat, 7 Sep 1996 11:23:28 -0500 (CDT)
From: Bob Willcox <bob@luke.pmr.com>
Reply-To: bob@pmr.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: panic: ufs_unlock NOT LOCKED
X-Send-Pr-Version: 3.2

>Number:         1579
>Category:       kern
>Synopsis:       panic: ufs_unlock NOT LOCKED
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    dyson
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Sep  7 09:30:01 PDT 1996
>Closed-Date:    Mon Oct 21 14:20:08 PDT 1996
>Last-Modified:  Mon Oct 21 14:21:03 PDT 1996
>Originator:     Bob Willcox
>Release:        FreeBSD 2.2-CURRENT i386
>Organization:
Power Micro Research
>Environment:

	2.2-current SUPed as of 9/6/96.  Note that this problem has been
	occuring for about two weeks through multiple SUPs and rebuilds.
	Unfortunately, I do not know the exact point in time at which it
	first occured.

>Description:

ufs_unlock: unlocked inode: type VBLK, usecount 2, writecount 0, refcount 3,
        tag VT_UFS, ino 815, on dev 4, 8

panic: ufs_unlock NOT LOCKED

>How-To-Repeat:

	Unmounting any of the file systems on this machine results in the
	panic.  Shutting down (halt, reboot, etc) also causes the panic
	as the system attempts to unmount the file systems.

>Fix:
	
	

>Release-Note:
>Audit-Trail:

From: "John S. Dyson" <toor@dyson.iquest.net>
To: bob@pmr.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/1579: panic: ufs_unlock NOT LOCKED
Date: Sat, 7 Sep 1996 11:57:11 -0500 (EST)

 > 
 > 
 > >Description:
 > 
 > ufs_unlock: unlocked inode: type VBLK, usecount 2, writecount 0, refcount 3,
 >         tag VT_UFS, ino 815, on dev 4, 8
 > 
 > panic: ufs_unlock NOT LOCKED
 > 
 If you need for your kernel to "work" right now, just build it without
 options DIAGNOSTIC.  I am going to attempt to reproduce/fix it right now.
 
 John
Responsible-Changed-From-To: freebsd-bugs->dyson 
Responsible-Changed-By: wosch 
Responsible-Changed-When: Thu Sep 26 17:15:22 PDT 1996 
Responsible-Changed-Why:  
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Mon Oct 21 14:20:08 PDT 1996 
State-Changed-Why:  
From Philippe Charnier: 
Could you please also close kern/1540 (solved by John Dyson). Note that 
kern/1579 (from Bob Willcox, bob@luke.pmr.com) is duplicate of kern/1540. 
done. 
>Unformatted:
