panic: trap type NUM, code=NUM, pc=NUM

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 958846eeae53 sync
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11ea4b73f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=92ab693480a297257c7a

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

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

panic: trap type 6, code=10, pc=0
Starting stack trace...
panic(ffffffff82564dbf) at panic+0x155 sys/kern/subr_prf.c:233
kerntrap(ffff8000230bdcb0) at kerntrap+0x1b7 sys/arch/amd64/amd64/trap.c:313
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
end trace frame: 0x0, count: 254
End of stack trace.

dump to dev 4,1 not possible
rebooting...
SeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2 Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 1f5eaa37-9319-de71-8c79-d2e486f4a21c
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f2730: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.53
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> 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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.