panic: mi_switch: switch in a critical section

Reply: Konstantin Belousov : "Re: panic: mi_switch: switch in a critical section"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Bjoern A. Zeeb <bzeeb-lists_at_lists.zabbadoz.net>
Date: Fri, 11 Jul 2025 08:56:04 UTC

# sysctl debug.kdb.enter=1 
db> cont
panic: mi_switch: switch in a critical section
cpuid = 3
time = 1752224052
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe007a575d00
vpanic() at vpanic+0x136/frame 0xfffffe007a575e30
panic() at panic+0x43/frame 0xfffffe007a575e90
mi_switch() at mi_switch+0x1b7/frame 0xfffffe007a575eb0
ast_scheduler() at ast_scheduler+0x45/frame 0xfffffe007a575ed0
ast_handler() at ast_handler+0xe8/frame 0xfffffe007a575f10
ast() at ast+0x20/frame 0xfffffe007a575f30
fast_syscall_common() at fast_syscall_common+0x1a2/frame 0xfffffe007a575f30
--- syscall (0, FreeBSD ELF64, syscall), rip = 0x9da5012b7aa, rsp = 0x9da4ce76fd8, rbp = 0x9da4ce77020 ---
KDB: enter: panic
[ thread pid 62399 tid 100210 ]
Stopped at      kdb_enter+0x33: movq    $0,0x103c492(%rip)


-- 
Bjoern A. Zeeb                                                     r15:7