On 8/15/23, Dag-Erling Smørgrav <d...@freebsd.org> wrote: > Dag-Erling Smørgrav <d...@freebsd.org> writes: >> I managed to geat a deadlock with 4e8d558c9d1c. Its predecessor >> 5ca7f02946 appears to be working. I'm going to try to come up with a >> more efficient way to reproduce the deadlock than running poudriere. > > I wrote a script that creates multiple filesystems, snapshots them, > populates them and rolls them back continuously but so far I have not > succeeded in triggering the deadlock without poudriere. I guess my > script doesn't consume enough vnodes. > > Also, 9228ac3a69c4 (9 August, last commit before the contrib/googletest > breakage) still deadlocks. >
Given that the custom reproducer failed I think the most prudent course of action is to reproduce again with poudriere, but this time arrange to have all stacktraces dumped. this should do it: sbin/ddb/ddb.conf:script kdb.enter.panic=textdump set; capture on; run lockinfo; show pcpu; bt; ps; alltrace; capture off; textdump dump; reset it is a slightly finicky beast so I would trigger a panic by hand first to validate it works as expected. -- Mateusz Guzik <mjguzik gmail.com>
