Ok, at the tail end of the dmesg file I am getting complaints starting at boot time of non-sleepable locks held. My source is current as of 12 hours ago. Pasted here is one of the errors: checking stopevent 2 with the following non-sleepable locks held: exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked _at_ /usr/src/sys/kern/kern_condvar.c:289 checking stopevent 2 with the following non-sleepable locks held: exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked _at_ /usr/src/sys/kern/subr_trap.c:260 checking stopevent 2 with the following non-sleepable locks held: exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked _at_ /usr/src/sys/kern/subr_trap.c:260 Thanks for the help Francis
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:29 UTC