Re: Hang on flushing buffers w/today's -CURRENT, SMP system

[Julian Elischer]

> 
> Eh; I suspect that's showing the entry to ddb.
> 
> Hmmm... gow about:
> 
> db> show witness
> Sleep locks:
> 0 Giant -- last acquired @ /usr/src/sys/kern/kern_intr.c:532
> 1  eventhandler -- last acquired @ /usr/src/sys/kern/subr_eventhandler.c:162
> 3    lockmgr -- last acquired @ /usr/src/sys/kern/kern_lock.c:227
> 4     malloc -- last acquired @ /usr/src/sys/kern/kern_malloc.c:303
> 5      zone -- last acquired @ /usr/src/sys/vm/vm_zone.c:506
> 1  pbuf mutex -- last acquired @ /usr/src/sys/vm/vm_pager.c:466
> 6       ucred -- last acquired @ /usr/src/sys/kern/kern_prot.c:1601
> 1  sf_bufs list lock -- last acquired @ /usr/src/sys/kern/uipc_syscalls.c:1556
> 4     malloc -- last acquired @ /usr/src/sys/kern/kern_malloc.c:303
> 3    lockmgr -- last acquired @ /usr/src/sys/kern/kern_lock.c:227

Looking at the ps I can't even see the process doing the exit..
it may be proc 0  or proc 1

can you trace them?
also 
show pcpu



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message