panic: thread ADDR cannotW ARexNiIt NGw:h ilSPeL h oNlOTdi nLgO WsElReEepD lOoNck sSY

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: dc36d2c7c3b1 correct Cd for fdt
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=133559c4c00000
kernel config: https://syzkaller.appspot.com/x/.config?x=3303344588104330
dashboard link: https://syzkaller.appspot.com/bug?extid=1a5e2edcaeeab34327db
compiler:

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

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+1a5e2e...@syzkaller.appspotmail.com

login: panic: thread 0xffff800020b939e0 cannotW ARexNiIt NGw:h ilSPeL h
oNlOTdi nLgO WsElReEepD lOoNck sSY
SCSALtLo pp95e d1 a4 tEXIT 0 9
db_enter+0x18: addq $0x8,%rsp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
116692 67475 73 0x100010 0 0 syslogd
*156780 12971 0 0x14000 0x200 1 reaper
db_enter() at db_enter+0x18 sys/arch/amd64/amd64/db_interface.c:399
panic() at panic+0x16c sys/kern/subr_prf.c:208
witness_thread_exit(8e2ffed4ec25a572) at witness_thread_exit+0x244
sys/kern/subr_witness.c:1377
reaper(0) at reaper+0x14f sys/kern/kern_exit.c:412
end trace frame: 0x0, count: 11
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

[Anton Lindqvist]

#syz dup: witness: thread exiting with locks held