Date: Fri, 18 Mar 2022 16:46:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262587] panic: lock (sleep mutex) umtxql not locked @ /usr/src/sys/sys/umtxvar.h:262 on 14-current master-n253798-8cdecdecb43 Message-ID: <bug-262587-227-euRLrfAOjG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262587-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262587 --- Comment #4 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Masachika ISHIZUKA from comment #3) Hmm, the inlining of umtxq_unlock() makes this hard to identify. Can you obtain a kernel dump? If not, you might try adding something like printf("linux futex op %d\n", args->op); to the beginning of linux_futex(), and reproduce the crash. That will make it easier to narrow down the code path; there are many uses of umtxq_unlock() in the futex code. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262587-227-euRLrfAOjG>