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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5d846028a9ec Explicitly request for battery status updates..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=125dcea1980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=768dab57b0824fdbfaff

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/16c4ce16322c/disk-5d846028.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/8c03b0183b28/bsd-5d846028.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/318225281ffa/kernel-5d846028.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+768dab...@syzkaller.appspotmail.com

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.


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup