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

0 views
Skip to first unread message

syzbot

unread,
Apr 28, 2026, 5:12:25 PM (16 hours ago) Apr 28
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6c5b951d135a Change xarray pool from IPL_NONE to IPL_TTY a..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=156d52ce580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=36f6f723cb14ad04c108

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/293678468828/disk-6c5b951d.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/a99581b4e6df/bsd-6c5b951d.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/804adbb8eeee/kernel-6c5b951d.xz

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

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>


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

Greg Steuck

unread,
Apr 28, 2026, 8:28:12 PM (13 hours ago) Apr 28
to syzbot, syzkaller-openbsd-bugs
#syz invalid 

--
You received this message because you are subscribed to the Google Groups "syzkaller-openbsd-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/69f122b7.050a0220.ac8b.0004.GAE%40google.com.
Reply all
Reply to author
Forward
0 new messages