Note: There was a bad value `' for the field `Class'.
	It was set to the default value of `sw-bug'.

>Number:         28705
>Category:       kern
>Synopsis:       2.0 kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Dec 18 20:18:00 +0000 2004
>Originator:     Dan McMahill
>Release:        NetBSD 2.0
>Organization:
NetBSD
>Environment:
	
	
System: NetBSD bondage 2.0 NetBSD 2.0 (BONDAGE) #0: Fri Dec 10 22:57:37 EST 2004 mcmahill@slashing:/usr/cvs/obj.alpha/sys/arch/alpha/compile/BONDAGE alpha
Architecture: alpha
Machine: alpha
>Description:

during a bulk pkgsrc build (not sure exactly where in the build, I was away),
I got a kernel panic with a 2.0 kernel.

stack trace:

db> bt
cpu_Debugger() at netbsd:cpu_Debugger+0x4
panic() at netbsd:panic+0x1f8
lockmgr() at netbsd:lockmgr+0x308
layer_unlock() at netbsd:layer_unlock+0x98
VOP_UNLOCK() at netbsd:VOP_UNLOCK+0x3c
vput() at netbsd:vput+0x5c
lookup() at netbsd:lookup+0x44c
namei() at netbsd:namei+0x1bc
sys___lstat13() at netbsd:sys___lstat13+0x5c
syscall_plain() at netbsd:syscall_plain+0xc4
XentSys() at netbsd:XentSys+0x5c
--- syscall (280) ---
--- user mode ---

	
>How-To-Repeat:
not sure.  I'll see if it happens again.  If there is any other info
I should get if it happens again, please let me know.
	
>Fix:
	

>Unformatted: