On a DS10L running NetBSD 2.0.2_STABLE built from the sources available 
near Jul 11th, I've
seen processes using bind/resolver get stuck in a 'saupcpl' state.  
They never return from this
state and cannot be killed (even when switching to single user mode).  
They can, however, be
suspended:

saupcpl  DW   ??   0:00.03 host 61.125
saupcpl  DW   p0-  0:00.02 host -t ns
saupcpl  DW   p2-  0:00.03 host 66.245
saupcpl  DW   p2-  0:00.02 host 66.245
saupcpl  DW   p3-  0:00.02 host
saupcpl  DW   p8-  0:00.02 nslookup ft
saupcpl  DW   p8-  0:00.02 host -vt mx
saupcpl  DW   pa-  0:00.02 nslookup
saupcpl  DW   pa-  0:00.02 nslookup
saupcpl  DW   pa-  0:00.02 nslookup
saupcpl  DW   pa-  0:00.02 nslookup we
saupcpl  DW   pd-  0:00.02 nslookup tw
saupcpl  DW   q2-  0:00.02 dig mx bac.
saupcpl  DW   q4-  0:00.02 nslookup ja
saupcpl  DW   q7-  0:00.03 host 66.245
saupcpl  DW   q9-  0:00.02 dig mx park
saupcpl  DW   r0-  0:00.02 host absent
saupcpl  DW   r0-  0:00.02 host absent
saupcpl  DW   r0-  0:00.02 host
saupcpl  DW   r0-  0:00.02 host absent
saupcpl  DW   r8-  0:00.03 host otaku
saupcpl  DW   r8-  0:00.02 host otaku
saupcpl  DW   ra-  0:00.02 dig any t1.
saupcpl  DW   rc-  0:00.04 nslookup 12
saupcpl  DW   rf-  0:00.03 dig reynald
saupcpl  DW   s0-  0:00.03 dig -t mx t
saupcpl  DW   s2-  0:00.02 host tortug
saupcpl  DW   s2-  0:00.02 nslookup ww
saupcpl  DW   s7-  0:00.02 dig any www
saupcpl  DW   ph-  0:00.02 dig -t mx t
saupcpl  DW   ph-  0:00.02 dig
saupcpl  DW   pi-  0:00.04 nslookup
saupcpl  DW   pi   0:00.02 nslookup pi
saupcpl  DW   pi   0:00.02 host pillar
saupcpl  DW   pk-  0:00.02 dig
saupcpl  DW   pk-  0:00.02 nslookup ww
saupcpl  DW   pm-  0:00.02 nslookup
saupcpl  DW   pq-  0:00.03 host -
saupcpl  DW   pq-  0:00.02 host -
saupcpl  DW   pq-  0:00.02 dig sumobas
saupcpl  DW   pv-  0:00.02 host mirand