Subject: processes block in vnlock
To: None <gnats-bugs@gnats.netbsd.org>
From: Johan Danielsson <joda@pdc.kth.se>
List: current-users
Date: 07/20/1999 12:48:34
>Submitter-Id:	net
>Originator:	Johan Danielsson
>Organization:
>Confidential:	no
>Synopsis:	processes block in vnlock
>Severity:	critical
>Priority:	high
>Category:	kern
>Class:		sw-bug
>Release:	~19990718
>Environment:
System: NetBSD blubb.pdc.kth.se 1.4G NetBSD 1.4G (BLUBB+CARDBUS) #110: Mon Jul 19 20:47:40 CEST 1999 joda@blubb.pdc.kth.se:/usr/misc/src/netbsd/netbsd-current/src/sys/arch/i386/compile/BLUBB+CARDBUS i386


>Description:

Sometimes processes blocks in vnlock. I've seen this when compiling in
emacs (when it's about to start the process), and when running su.

The blocked process looks like this:

    0  5422  5421   0  -2 -2    64  392 vnlock D<s+ p4    0:00.02 /usr/bin/su 

Typing a few characters in some other terminal usually unblocks the
process.

I assume this is because of some subtle bug in the recent vnode
locking changes. 

This is what I have mounted:

/dev/wd0a on / type ffs (local)
/dev/wd0e on /usr type ffs (local)
/dev/wd0f on /usr/misc type ffs (local)
/dev/wd0g on /usr/misc/src/netbsd type ffs (local)
mfs:307 on /tmp type mfs (asynchronous, local)
procfs on /proc type procfs (local)
kernfs on /kern type kernfs (local)
fdesc on /dev type fdesc (local, union)


>How-To-Repeat:

Hard to tell. It doesn't always happen, but I think it might happen
when I have forground processes running in some other terminal (but
this is just speculation).

>Fix:

Dunno.