Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Mar 2022 16:06:14 +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-FNrwpzfQTp@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-262587-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-262587-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=3D262587

Mark Johnston <markj@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markj@FreeBSD.org
             Status|New                         |Open

--- Comment #2 from Mark Johnston <markj@FreeBSD.org> ---
(In reply to Masachika ISHIZUKA from comment #0)
The panic is:

panic: lock (sleep mutex) umtxql not locked @ /usr/src/sys/sys/umtxvar.h:26=
2=20=20=20=20
cpuid =3D 2=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
time =3D 1647416763=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
KDB: stack backtrace:=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0101153=
c00=20=20
vpanic() at vpanic+0x17f/frame 0xfffffe0101153c50=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
panic() at panic+0x43/frame 0xfffffe0101153cb0=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
witness_unlock() at witness_unlock+0x144/frame 0xfffffe0101153cf0=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
__mtx_unlock_flags() at __mtx_unlock_flags+0x4d/frame 0xfffffe0101153d20=20=
=20=20=20=20=20=20=20
linux_sys_futex() at linux_sys_futex+0x5e1/frame 0xfffffe0101153e00=20=20=
=20=20=20=20=20=20=20=20=20=20=20
amd64_syscall() at amd64_syscall+0x12e/frame 0xfffffe0101153f30=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe0101153f30=
=20=20=20=20=20=20
--- syscall (202, Linux ELF64, linux_sys_futex), rip =3D 0x803a0ba35, rsp =
=3D
0x8061d0c90, rbp =3D 0x8061d0dc0 ---

I'm not sure which call to umtxq_unlock() this corresponds to.

There are no changes to the linuxulator in that range of revisions, but your
version string is "master-n253798-8cdecdecb43-dirty", so you have some local
changes.  Any in the linuxulator?  If not, please try installing gdb and
running:

# kgdb -q
(kgdb) list *linux_sys_futex+0x5e1

and show the output.

--=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-262587-227-FNrwpzfQTp>