Date: Tue, 1 Oct 2024 11:53:28 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: dsdqmzk@hotmail.com Cc: current@freebsd.org Subject: Re: panic: curthread not pinned Message-ID: <Zvu4iAjS-Vb9HZS1@kib.kiev.ua> In-Reply-To: <SEYPR02MB5821FCD0714AE0F0B19EDAADB1772@SEYPR02MB5821.apcprd02.prod.outlook.com> References: <SEYPR02MB5821FCD0714AE0F0B19EDAADB1772@SEYPR02MB5821.apcprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 01, 2024 at 01:16:31PM +0700, dsdqmzk@hotmail.com wrote: > Hyper-V Gen2 VM, 8 cores, 8GB RAM. The panic is reproducible while > running `make -j8 buildworld`. Initially installed from > FreeBSD-15.0-CURRENT-amd64-20240926-6a4f0c063718-272495-disc1.iso, > updating the kernel (that I could build) to b35f0aa4952 does not help. > > panic: curthread not pinned > cpuid = 3 > time = 1727763183 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe008e34a1f0 > vpanic() at vpanic+0x13f/frame 0xfffffe008e34a320 > panic() at panic+0x43/frame 0xfffffe008e34a380 > smp_targeted_tlb_shootdown_native() at > smp_targeted_tlb_shootdown_native+0x472/frame 0xfffffe008e34a4c0 > pmap_remove_all() at pmap_remove_all+0x560/frame 0xfffffe008e34a540 Can you obtain the core dump and then backtrace from kgdb?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zvu4iAjS-Vb9HZS1>