panic: trap type NUM, code=NUM, pc=NUM (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a7d38a062623 Link http regress test with -lz for content-e..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=145517fd280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=d46528b28cec2ed0e9a1

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1b1f514ae65e/disk-a7d38a06.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/a079cfc358d9/bsd-a7d38a06.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fd8489b430e8/kernel-a7d38a06.xz

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

panic: trap type 6, code=10, pc=0
Starting stack trace...
panic(ffffffff827863e7) at panic+0x16f sys/kern/subr_prf.c:229
kerntrap(ffff8000211b8c10) at kerntrap+0x1d7 sys/arch/amd64/amd64/trap.c:336
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
0(fffffd8079a34f00,fffffd8079a34f00,0,fffffd8079a34f00,46a,0) at 0
softclock_process_kclock_timeout(fffffd8079a34f00,0) at softclock_process_kclock_timeout+0x1ca sys/kern/kern_timeout.c:666
softclock(0) at softclock+0x11a sys/kern/kern_timeout.c:717
softintr_dispatch(0) at softintr_dispatch+0xfb sys/arch/amd64/amd64/softintr.c:90
Xsoftclock() at Xsoftclock+0x23
Xspllower() at Xspllower+0x1d
printf(ffffffff82773fcb) at printf+0x88 sys/kern/subr_prf.c:532
uvm_fault_unwire_locked(fffffd806efef578,a4496404000,a4496603000) at uvm_fault_unwire_locked+0x20c sys/uvm/uvm_fault.c:1679
uvm_unmap_kill_entry_withlock(fffffd806efef578,fffffd8067c2d268,0) at uvm_unmap_kill_entry_withlock+0x6b sys/uvm/uvm_map.c:1925
uvm_map_teardown(fffffd806efef578) at uvm_map_teardown+0x197 uvm_map_addr_RBT_LEFT sys/uvm/uvm_map.h:176 [inline]
uvm_map_teardown(fffffd806efef578) at uvm_map_teardown+0x197 sys/uvm/uvm_map.c:2565
uvmspace_free(fffffd806efef578) at uvmspace_free+0xa6 sys/uvm/uvm_map.c:3503
reaper(ffff8000211ac578) at reaper+0x19a sys/kern/kern_exit.c:449
end trace frame: 0x0, count: 242
End of stack trace.

dump to dev 4,1 not possible
rpebooatinincg..:.
kernel diagSeaBIOS (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 fe2172e1-0ae4-3e3c-d45b-fa0270c0bf41
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 0x000f2850: 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.56
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.

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

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

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

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