panic: thread NUM p_stat is NUM (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3800fc3581d8 Add sensors based on information in the SMART..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=177a67c7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=89d97c38c08f46f581de

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/248090d6018d/disk-3800fc35.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/5d113e172266/bsd-3800fc35.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e320dfdaabf5/kernel-3800fc35.xz

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

panic: thread 0 p_stat is 0
Stopped at db_enter+0SeaBIOS (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 f8e08a03-81bc-3227-53c0-939594373760
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 0x000f27c0: 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> 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 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