[Bug 249149] panic: -CURRENT with KCSAN option -> panic: mtx_lock_spin: recursed on non-recursive mutex et_hw_mtx @ src/sys/kern/kern_clocksource.c:850

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249149

            Bug ID: 249149
           Summary: panic: -CURRENT with KCSAN option -> panic:
                    mtx_lock_spin: recursed on non-recursive mutex
                    et_hw_mtx @ src/sys/kern/kern_clocksource.c:850
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs at FreeBSD.org
          Reporter: gbe at FreeBSD.org

Created attachment 217791
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=217791&action=edit
-CURRENT dmesg with KCSAN messages and the kernel panic

On a virtualized amd64 VM (Hyper-V) of -CURRENT r365373 the system panics
reproducible with a KCSAN enabled kernel.

The KERNCONF is the following:
include GENERIC
ident GENERIC-SANTI
options         KCSAN
options         RATELIMIT
options         TCPHPTS
options         KERN_TLS

The full panic message with the stacktrace is the following
panic: mtx_lock_spin: recursed on non-recursive mutex et_hw_mtx @
/boiler/nfs/src/sys/kern/kern_clocksource.c:850

cpuid = 0
time = 1599396342
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x34/frame 0xfffffe0006e74030
kdb_backtrace() at kdb_backtrace+0x6a/frame 0xfffffe0006e740e0
vpanic() at vpanic+0x229/frame 0xfffffe0006e74130
panic() at panic+0x53/frame 0xfffffe0006e74190
_mtx_lock_spin_cookie() at _mtx_lock_spin_cookie/frame 0xfffffe0006e741f0
cpu_new_callout() at cpu_new_callout+0xc5/frame 0xfffffe0006e74240
callout_cc_add() at callout_cc_add+0x2aa/frame 0xfffffe0006e742a0
callout_reset_sbt_on() at callout_reset_sbt_on+0x5ce/frame 0xfffffe0006e74340
callout_schedule() at callout_schedule+0x76/frame 0xfffffe0006e74380
vtterm_post_input() at vtterm_post_input+0xa6/frame 0xfffffe0006e743a0
termteken_post_input() at termteken_post_input+0x2e/frame 0xfffffe0006e743c0
teken_input() at teken_input+0x1f8/frame 0xfffffe0006e74420
termcn_cnputc() at termcn_cnputc+0xa7/frame 0xfffffe0006e74460
cnputc() at cnputc+0x80/frame 0xfffffe0006e744a0
cnputs() at cnputs+0x90/frame 0xfffffe0006e744d0
putchar() at putchar+0x236/frame 0xfffffe0006e74580
kvprintf() at kvprintf+0xfa7/frame 0xfffffe0006e746d0
vprintf() at vprintf+0x9b/frame 0xfffffe0006e747b0
printf() at printf+0x53/frame 0xfffffe0006e74810
kcsan_access() at kcsan_access+0x19b/frame 0xfffffe0006e748f0
lapic_et_start() at lapic_et_start+0x628/frame 0xfffffe0006e74940
et_start() at et_start+0xdd/frame 0xfffffe0006e74980
loadtimer() at loadtimer+0x1ef/frame 0xfffffe0006e749d0
handleevents() at handleevents+0x401/frame 0xfffffe0006e74a30
cpu_activeclock() at cpu_activeclock+0xd0/frame 0xfffffe0006e74a70
cpu_idle() at cpu_idle+0xea/frame 0xfffffe0006e74aa0
sched_idletd() at sched_idletd+0x5de/frame 0xfffffe0006e74bb0
fork_exit() at fork_exit+0xaa/frame 0xfffffe0006e74bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0006e74bf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic

-- 
You are receiving this mail because:
You are the assignee for the bug.