The following reply was made to PR kern/29670; it has been noted by GNATS.

From: Ken Raeburn <raeburn@raeburn.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/29670: "release of unlocked lock" panic with null fs
Date: Tue, 15 Mar 2005 06:27:29 -0500

 At Martin Husemann's suggestion, I installed a new kernel with 
 LOCKDEBUG enabled, and when the cron job kicked off again, the machine 
 panicked again, and hung with a stack trace displayed:
 
 [output scrolled off screen]pages+0x66c
 VOP_PUTPAGES+0x40
 ffs_full_fsync+0x342
 ffs_fsync+0x4b
 VOP_FSYNC+0x4c
 ffs_sync+0x29a
 sys_sync+0x105
 vfs_shutdown+0x5f
 cpu_reboot+0x103
 panic+0x108
 _lockmgr+0xeb
 layer_unlock+0x56
 VOP_UNLOCK+0x28
 layer_inactive+0x15
 VOP_INACTIVE+0x28
 vput+0x11a
 lookup+0x283
 namei+0x138
 sys_access+0x75
 syscall_plain+0x7e
 
 When I tried ctrl+alt+esc to get a stack trace from the kernel 
 debugger, the active process was aiodoned, and none of this was in the 
 stack trace.  Without the initial messages, though, I don't know for 
 sure if this is an instance of the same problem, or something 
 different.  Will keep watching for more problems....
 
 Ken