Hi,

I have recently been experiencing som mysterous hangs when using LFS.
All disk activity would cease, but the system would still respond to
network and console activity.  I built a new kernel with LOCKDEBUG
enabled, and soon after I started activities on the LFS, I got a slew
of console messages:

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

This is with NetBSD-current as of today on an Alpha PC164.  Is there
anyone that will immediately spot what might be wrong?
					-jarle
-- 
"Your brand new kernel just dump core on you -- and fsck can't find inode 2
 Don't worry -- be happy..."