netbsd boot error: panic: LO0KatBUGsiMus0 targer i_nw0tch,o28:espPersict heDis[ ADDR]kc u1:diekiniteac

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 9695800e Panic instead of printf, same as syscall.
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=172b9e41e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=824b23e1f4b6c76b
dashboard link: https://syzkaller.appspot.com/bug?extid=bcc92ac68d330cddf7c2
compiler: g++ (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609

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+bcc92a...@syzkaller.appspotmail.com

[ 1.5671779] panic: LO0KatBUGsiMus0 targer i_nw0tch,o28:espPersict
heDis[ 1156771779]kc u1:diekiniteac
1.[ 7.93 b2c7..s
1.6351227] d0: fabricating a geometry
[ 1.6351227] sd0: 8192 MB, 8192 cyl, 64 head, 32 sec, 512 bytes/sect x
16777216 sectors
[ 1.6486547] sd0: fabriic() ata geometry
[ 1.[48 5.6] s50:] netb, 8vpin traxsfe
1.6486547] rs, tagged queueing
[ 1.6771659] snprintf() at netbsd:snprintf
[ 1.6972139] lockdebug_abort1() at netbsd:lockdebug_abort1+0x16e
sys/kern/subr_lockdebug.c:799
[ 1.7272669] lockdebug_barrier() at netbsd:lockdebug_barrier+0x157
sys/kern/subr_lockdebug.c:673
[ 1.7373093] mi_switch() at netbsd:mi_switch+0xbf
sys/kern/kern_synch.c:532
[ 1.7373093] idle_loop() at netbsd:idle_loop+0x4bf x86_curlwp
sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./machine/cpu.h:79 [inline]
[ 1.7373093] idle_loop() at netbsd:idle_loop+0x4bf sys/kern/kern_idle.c:99
[ 1.7373093] cpu_hatch() at netbsd:cpu_hatch+0x3a7
sys/arch/x86/x86/cpu.c:970
[ 1.7373093] cpu1: End traceback...
[ 1.7373093] fatal breakpoint trap in supervisor mode
[ 1.7373093] trap type 1 code 0 rip 0xffffffff8021dd9d cs 0x8 rflags
0x282 cr2 0 ilevel 0x8 rsp 0xffffba00a57c6d30
[ 1.7373093] curlwp 0xffff8dd06d058100 pid 0.20 lowest kstack
0xffffba00a57c32c0
Stopped in pid 0.20 (system) at netbsd:breakpoint+0x5: leave
db{1}>


---
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#status for how to communicate with syzbot.

[Maxime Villard]

dismiss

#syz invalid