Date: Tue, 08 Feb 2022 02:41:42 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 261198] bhyve host panics with: spin lock 0xffffffff81eac800 (callout) helpanic: spin lock held too long Message-ID: <bug-261198-27103-UXYmTVkTX9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261198-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-261198-27103@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261198 --- Comment #7 from Mark Johnston <markj@FreeBSD.org> --- Hmm, I wonder if we can avoid stopping the callout when td->td_lock != sc->sc_lock. In that case, the thread is in the process of going to sleep and will abort in sleepq_switch() anyway. I don't think sleepq_switch() can safely abort the callout, but I believe it should be ok to leave it be. That'd be a rare case, and see the comment above the problematic callout_stop() call. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261198-27103-UXYmTVkTX9>