syzbot


panic: thread NUM p_stat is NUM (2)

Status: upstream: reported on 2024/09/14 06:14
Reported-by: syzbot+89d97c38c08f46f581de@syzkaller.appspotmail.com
First crash: 14d, last: 14d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd panic: thread NUM p_stat is NUM 1 168d 168d 0/3 auto-obsoleted due to no activity on 2024/07/12 13:03

Sample crash report:
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

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/09/14 06:13 openbsd 3800fc3581d8 ff60e2ca .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: thread NUM p_stat is NUM
* Struck through repros no longer work on HEAD.