Subject: kern/498: panic: ufs_unlock NOT LOCKED
To: None <gnats-admin@sun-lamp.cs.berkeley.edu>
From: Havard Eidnes <Havard.Eidnes@runit.sintef.no>
List: netbsd-bugs
Date: 09/26/1994 13:05:04 
>Number:         498
>Category:       kern
>Synopsis:       panic: ufs_unlock NOT LOCKED
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    gnats-admin (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 26 13:05:03 1994
>Originator:     Havard Eidnes
>Organization:
"	SINTEF RUNIT"
>Release:        NetBSD 1.0_Beta
>Environment:
System: NetBSD lirype.runit.sintef.no 1.0_BETA NetBSD 1.0_BETA (LIRYPE) #0: Sat Sep 24 20:39:04 MET DST 1994     he@lirype.runit.sintef.no:/usr/src/sys/arch/hp300/compile/LIRYPE hp300

>Description:
	The panic was produced by the following sequence of actions:

	# ln -s /usr/local /local
	# mkdir /local/src
	# cd /local/src
	# mount rype:/local/src /local/src
	# ls

	poof...

	The panic string was "panic: ufs_unlock NOT LOCKED".

>How-To-Repeat:
	See above
>Fix:
	Sorry, again out of my league.  This is admittedly "strange usage".
>Audit-Trail:
>Unformatted: