syzbot


panic: db_mtx_enter: mtx ADDR: locking against myself

Status: auto-obsoleted due to no activity on 2023/12/09 11:42
Reported-by: syzbot+c74cf896283b8b8c5a3c@syzkaller.appspotmail.com
First crash: 438d, last: 438d

Sample crash report:
wpanic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
kernel: double fault trap, code=0
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
panic: db_mtx_enter: mtx 0xffffffff82cff368: locking against myself
SeaBIOS (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 b0453e05-8c57-eb46-d253-85f0946d26d2
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 0x000f2880: 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.65
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
2023/09/10 11:41 openbsd fc516a654004 6654cf89 .config console log report ci-openbsd-setuid panic: db_mtx_enter: mtx ADDR: locking against myself
* Struck through repros no longer work on HEAD.