netbsd boot error: panic: sOC DEBsGs Muse tergot 2 i_s 0: <G52o8l , Pe loctenheld

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: e54bc46e need pfilter.h
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=16c11edae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=824b23e1f4b6c76b
dashboard link: https://syzkaller.appspot.com/bug?extid=1f711ef217e38f4989e9
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+1f711e...@syzkaller.appspotmail.com

[ 1.5436573] panic: sOC DEBsGs Muse tergot 2 i_s 0: <G52o8l , Pe
loctenheld
[ 1.5436573] ,p1> diekin xedceba[ 1.543[ 31 c917.8
] sd0: fabricating a geometry
[ 1.5917388] sd0: 8192 MB, 8192 cyl, 64 head, 32 sec, 512 bytes/sect x
16777216 sectors
[ 1.6006219] sd0: fabricating a geometry
[ 1.6039190] vpanic() at netbsd:vpanic+0x2aa sys/kern/subr_prf.c:336
[ 1.6234962] snprintf() at sd0: async, 8-bit transfers, tagged queueing
[ 1.6351959] netbsd:snprintf
[ 1.6535436] lockdebug_abort1() at netbsd:lockdebug_abort1+0x16e
sys/kern/subr_lockdebug.c:799
[ 1.6735728] lockdebug_barrier() at netbsd:lockdebug_barrier+0x157
sys/kern/subr_lockdebug.c:673
[ 1.6835892] mi_switch() at netbsd:mi_switch+0xbf
sys/kern/kern_synch.c:532
[ 1.6835892] idle_loop() at netbsd:idle_loop+0x4bf x86_curlwp
sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./machine/cpu.h:79 [inline]
[ 1.6835892] idle_loop() at netbsd:idle_loop+0x4bf sys/kern/kern_idle.c:99
[ 1.6835892] cpu_hatch() at netbsd:cpu_hatch+0x3ac
sys/arch/x86/x86/cpu.c:980
[ 1.6835892] cpu1: End traceback...
[ 1.6835892] fatal breakpoint trap in supervisor mode
[ 1.6835892] trap type 1 code 0 rip 0xffffffff8021dd9d cs 0x8 rflags
0x282 cr2 0 ilevel 0x8 rsp 0xffffc800a57c6d30
[ 1.6835892] curlwp 0xffffb4d5d4e58100 pid 0.20 lowest kstack
0xffffc800a57c32c0
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