syzbot


panic: curcpu->ci_proc_pmap didn't point to previous pmap (2)

Status: upstream: reported on 2025/11/24 18:56
Reported-by: syzbot+a25725fab050c1ca28eb@syzkaller.appspotmail.com
First crash: 4d23h, last: 4d23h
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd panic: curcpu->ci_proc_pmap didn't point to previous pmap 2 1 491d 491d 0/3 auto-obsoleted due to no activity on 2024/10/24 03:48

Sample crash report:
panic: curcpu->ci_proc_pmap didn't point to previous pmap
Starting stack trace...
panic(ffffffff835f5b7d) at panic+0x1d0 sys/kern/subr_prf.c:229
switch_restored() at switch_restored+0x3f
sleep_finish(989680,1) at sleep_finish+0x2d8 sys/kern/kern_synch.c:367
sys_nanosleep(ffff80003bff6030,ffff80003c4c3800,ffff80003c4c3750) at sys_nanosleep+0x26a sys/kern/kern_time.c:303
syscall(ffff80003c4c3800) at syscall+0xbd4 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003c4c3800) at syscall+0xbd4 sys/arch/amd64/amd64/trap.c:765
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7e2da602f7c0, count: 251
End of stack trace.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/11/24 18:55 openbsd 879ea5f6fdb7 bf6fe8fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: curcpu->ci_proc_pmap didn't point to previous pmap
* Struck through repros no longer work on HEAD.