netbsd boot error: panic: taKDEBUG:lunt0: eGrog:e, Psrsicte5tDisk,in> ockkheixe

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 17de466e loadfile sets errno, return the correct error, no..
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=158a459ce00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6e4d6bd2b8e377a2
dashboard link: https://syzkaller.appspot.com/bug?extid=fa91008fad0ef6d8e3c2
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+fa9100...@syzkaller.appspotmail.com

[ 1.9361712] panic: taKDEBUG:lunt0: eGrog:e, Psrsicte5tDisk,in> ockkheixe
..9617712] cpu1
1.9361712] Begin traceback...
[ 1.9587751] sd0: fabricating a geometry
[ 1.9587751] sd0: 8192 MB, 8192 cyl, 64 head, 32 sec, 512 bytes/sect x
16777216 sectors
[ 1.9773425] vpanic() at sd0: fabricating a geometry
[ 1.9876652] netbsd:vpanic+0x241
[ 2.0350195] snprintf() at netbsd:snprintf
[ 2.0350195] lockdebug_more() at netbsd:lockdebug_more
[ 2.0350195] lockdebug_barrier() at netbsd:lockdebug_barrier+0xfe
sys/kern/subr_lockdebug.c:684
[ 2.0350195] mi_switch() at netbsd:mi_switch+0xfb
sys/kern/kern_synch.c:532
[ 2.0350195] idle_loop() at netbsd:idle_loop+0x34a x86_curlwp
sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./machine/cpu.h:79 [inline]
[ 2.0350195] idle_loop() at netbsd:idle_loop+0x34a sys/kern/kern_idle.c:99
[ 2.0350195] cpu_hatch() at netbsd:cpu_hatch+0x267
sys/arch/x86/x86/cpu.c:970
[ 2.0350195] Bad frame pointer: 0xffffdc000f738100
[ 2.0350195] cpu1: End traceback...
[ 2.0350195] fatal breakpoint trap in supervisor mode
[ 2.0350195] trap type 1 code 0 rip 0xffffffff8021ccc5 cs 0x8 rflags
0x246 cr2 0 ilevel 0x8 rsp 0xffffdc016db37b50
[ 2.0350195] curlwp 0xffffdc000f738100 pid 0.20 lowest kstack
0xffffdc016db302c0
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