syzbot


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

Status: closed as invalid on 2026/04/29 00:28
Reported-by: syzbot+36f6f723cb14ad04c108@syzkaller.appspotmail.com
First crash: 22h53m, last: 22h53m

Sample crash report:
panic: acquiring blockable slSeaBIOS (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 dc1537e2-3f8b-09d0-7a97-ada6c38139e5
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 0x000f26f0: 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> 

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/28 21:11 openbsd 6c5b951d135a 340bcdf0 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: acquiring blockable slSeaBIOS (version NUM.NUM.NUM-google)
* Struck through repros no longer work on HEAD.