syzbot


panic: acquiring blockable sleSeaBIOS (version NUM.NUM.NUM-google)

Status: upstream: reported on 2026/04/03 00:24
Reported-by: syzbot+6459083defb530c9c8d8@syzkaller.appspotmail.com
First crash: 8d08h, last: 8d08h

Sample crash report:
panic: acquiring blockable sleSeaBIOS (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 479bd2e4-6073-186a-8c25-a69e4074584d
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> 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> 

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/03 00:24 openbsd 38cd3ff5d287 4b3d9a38 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: acquiring blockable sleSeaBIOS (version NUM.NUM.NUM-google)
* Struck through repros no longer work on HEAD.