From owner-freebsd-bugs  Sat Sep  7 09:30:04 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA16438
          for bugs-outgoing; Sat, 7 Sep 1996 09:30:04 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA16430;
          Sat, 7 Sep 1996 09:30:02 -0700 (PDT)
Resent-Date: Sat, 7 Sep 1996 09:30:02 -0700 (PDT)
Resent-Message-Id: <199609071630.JAA16430@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, bob@pmr.com
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
X-Send-Pr-Version: 3.2
Subject: kern/1579: panic: ufs_unlock NOT LOCKED
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         1579
>Category:       kern
>Synopsis:       panic: ufs_unlock NOT LOCKED
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Sep  7 09:30:01 PDT 1996
>Last-Modified:
>Originator:     Bob Willcox
>Organization:
Power Micro Research
>Release:        FreeBSD 2.2-CURRENT i386
>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:
	
	

>Audit-Trail:
>Unformatted: