>Number:         11525
>Category:       kern
>Synopsis:       LFS + LOCKDEBUG produce warning messages
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 19 10:32:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Jarle Greipsland
>Release:        NetBSD-current 2000-11-19
>Organization:
RUNIT as
>Environment:
	
System: NetBSD honey.runit.no 1.5K NetBSD 1.5K (HONEY-$Revision: 1.130 $) #11: Sun Nov 19 18:00:02 CET 2000     jarle@honey.runit.no:/usr/src/sys/arch/alpha/compile/HONEY alpha


>Description:
When using LFS with a kernel configured with the LOCKDEBUG option, the
following messages appear on the console:

simple_lock: lock held
lock: 0xfffffc0002cd50d0, currently at: ../../../../kern/vfs_subr.c:1257
last locked: ../../../../kern/vfs_subr.c:1190
last unlocked: ../../../../kern/vfs_subr.c:1281
simple_unlock: lock not held
lock: 0xfffffc0002cd50d0, currently at: ../../../../kern/vfs_subr.c:1193
last locked: ../../../../kern/vfs_subr.c:1257
last unlocked: ../../../../kern/vfs_subr.c:1281

This doesn't look healthy to me.  Note that the messages occur every now
and then, but always with the same lock value.

The reason I configured the kernel with the LOCKDEBUG options is that I
have recently been seeing some problems where the kernel would lock up and
no file system activities would take place.  However, it would still
respond to network and console input, as long as nothing required data from
any file system.
	
>How-To-Repeat:

Configure a kernel with LFS and LOCKDEBUG.  Run some programs that will put
load on the an LFS-based file system.

	
>Fix:
	
Unknown -- at least to me.
>Release-Note:
>Audit-Trail:
>Unformatted: