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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 879ea5f6fdb7 Update to reflect support for special keys.
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=168cf97c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=a25725fab050c1ca28eb

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5cdfa60cfda3/disk-879ea5f6.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/446b64d9feca/bsd-879ea5f6.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7ba09c19069c/kernel-879ea5f6.xz

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

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.


---
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