[Bug 281560] gve (4) uma deadlock during high tcp throughput

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281560

--- Comment #3 from Konstantin Belousov <kib@FreeBSD.org> ---
If you have WITNESS configured, then you can get an overview of the locks
ownership on the system, using the 'show alllocks' ddb command.  This should
allow you to see lock owners, including the shared locks (like read-locked
rwlocks).  Another hint is that ddb 'ps' command output wchan ia the address
of lock (or something very close to it) where the thread blocked.

This should be enough to see the loops.  Basically, take any blocked thread,
see which lock it needs ('ps'), then find a thread that owns the lock.  Now
look at the backtrace of the lock owner and see why it does not make progress,
e.g. typically waiting for yet another lock, and so on.

-- 
You are receiving this mail because:
You are the assignee for the bug.