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

Status: auto-obsoleted due to no activity on 2024/10/24 03:48
Reported-by: syzbot+768dab57b0824fdbfaff@syzkaller.appspotmail.com
First crash: 767d, last: 767d
▶ ▼ Similar bugs (2)
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 (3) 2 1 161d 161d 0/4 auto-obsoleted due to no activity on 2026/06/22 08:50
openbsd panic: curcpu->ci_proc_pmap didn't point to previous pmap (2) 2 1 280d 280d 0/4 auto-obsoleted due to no activity on 2026/02/22 18:56

Sample crash report:
panic: curcpu->ci_proc_pmap didn't point to previous pmap
Starting stack trace...
panic(ffffffff833621dd) at panic+0x1d0 sys/kern/subr_prf.c:229
switch_restored() at switch_restored+0x3f
preempt() at preempt+0x6a sys/kern/sched_bsd.c:338
ast(ffff800037286c10) at ast+0x165 mi_ast sys/sys/syscall_mi.h:261 [inline]
ast(ffff800037286c10) at ast+0x165 sys/arch/amd64/amd64/trap.c:541
intr_user_exit() at intr_user_exit+0x3c
end trace frame: 0x0, count: 252
End of stack trace.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/07/26 03:47 openbsd 5d846028a9ec 3f86dfed .config console log report ci-openbsd-multicore panic: curcpu->ci_proc_pmap didn't point to previous pmap
* Struck through repros no longer work on HEAD.