https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219216
--- Comment #1 from Konstantin Belousov <k...@freebsd.org> --- The description of the problem is not very useful. When the panic 'spinlock held too long' occurs, presumably for the sched locks, catch exact kernel messages (same as you did) and also the backtrace for the thread which is reported as the owner of the spinlock. I will see if more information is needed after that. Note that if CPU speed is artificially reduced, then spinlock sections might take much longer time to execute, which would, in turn, trigger the detector for the stuck spinlock. I do not claim that this is your case, but it could be. sched_bind() does not depend on rnd. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
