https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281560
--- Comment #2 from shail...@google.com --- Actually I did run it with INVARIANTS and WITNESS and other options listed on https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-deadlocks and the deadlock reproduces without any findings from INVARIANTS or WITNESS. `procstat -k ${tid?}` is the only only tool I know to look at the deadlocked threads and that hints at some locking issue in the uma zone cache (as per the per-thread procstat -k in comment #0). Are there some other ways I can look at the locked threads and more definitively figure out what resource they are blocked on and who owns it? -- You are receiving this mail because: You are the assignee for the bug.
