panic: init died (signal NUM, exit NUM) (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2f434a4256f3 Bump version to 9.1
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17f10116580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=fd4a5b454cf93f84b044

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/064d43172290/disk-2f434a42.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/e1c14fbda677/bsd-2f434a42.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8f7c9e8e2f6/kernel-2f434a42.xz

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

panic: init died (signal 0, exit 8)
Starting stack trace...
panic(ffffffff834263b6) at panic+0x1ba sys/kern/subr_prf.c:229
exit1(ffff80002a6fdc88,8,0,1) at exit1+0x127 sys/kern/kern_exit.c:135
sys_exit(ffff80002a6fdc88,ffff80002a6fb740,ffff80002a6fb690) at sys_exit+0x1a sys/kern/kern_exit.c:-1
syscall(ffff80002a6fb740) at syscall+0x962 mi_syscall sys/sys/syscall_mi.h:-1 [inline]
syscall(ffff80002a6fb740) at syscall+0x962 sys/arch/amd64/amd64/trap.c:783
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7b79053cc240, count: 252
End of stack trace.
syncing disks...38 34 done

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 9c8ab089-5fb3-144b-a4ba-2e178800b25c
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 0x000f26c0: 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.67
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot>


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