Issue #2291 has been updated by Venkatesh Srinivas. Status changed from New to Resolved
Commit 24624a1562837ae797e4c1b05689f6f5b56006d9 prevents the latter two panics. I believe this issue is resolved. ---------------------------------------- Bug #2291: Panic in lwkt_remove_tdallq http://bugs.dragonflybsd.org/issues/2291 Author: Rumko Rumko Status: Resolved Priority: Normal Assignee: Category: Target version: With a few days old master and under some I/O load I get the mentioned panic (the actual panic message is illegable, only the trace can be read) ... was unable to get a core dump (panic in ddb didn't produce a dump, only rebooted the machine). The panic seems to be easily repeatable (unfortunately this is the first time I actually saw a trace, because I had DDB_UNATTENDED switched on before + was in X, so could not see the message) Part of the backtrace (only the function names, I managed to take pictures of the backtrace itself, attached to this report): panic() lwkt_remove_tdallq() free_lock() acquire_lock() softdep_disk_io_initiation() devfs_spec_strategy() vop_strategy() vn_strategy() ufs_strategy() ufs_vnoperate() vop_strategy() vn_strategy() bawrite() ... syncer_thread() syncer_thread_start() kthread_exit() -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
