Date: Tue, 27 Oct 2020 14:02:51 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2) Message-ID: <bug-250667-227-5WMUlskRqo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250667-227@https.bugs.freebsd.org/bugzilla/> References: <bug-250667-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250667 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markj@FreeBSD.org Status|New |Open --- Comment #1 from Mark Johnston <markj@FreeBSD.org> --- We're panicking because an idle thread is processing callouts and apparently taking too long. Unfortunately I can't see what it was actually doing. Th= ere aren't many users of C_DIRECT_EXEC but it's possible the thread is somehow stuck in a callout handler. It's possible that some memory corruption is causing callout_process() to loop infinitely on a callout list. I don't think it'll be easy to debug this without a vmcore: https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerne= ldebug.html#kerneldebug-obtain --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250667-227-5WMUlskRqo>