netbsd boot error: assert failed: start < end

0 views
Skip to first unread message

syzbot

unread,
Jan 28, 2022, 12:34:18 AM1/28/22
to syzkaller-...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 18e3a769564f numEntries can vary
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=12526937b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=1420f906d33d9f1f
dashboard link: https://syzkaller.appspot.com/bug?extid=bbf8128f34cf499580b5
compiler: g++ (Debian 10.2.1-6) 10.2.1 20210110

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

[ 1.6351781] panic: kernel diagnostic assertion "start < end" failed: file "/syzkaller/managers/ci2-netbsd-kubsan/kernel/sys/uvm/uvm_km.c", line 513
[ 1.6502803] cpu0: Begin traceback...
[ 1.6539949] vpanic() at netbsd:vpanic+0x2d0 sys/kern/subr_prf.c:290
[ 1.6936978] kern_assert() at netbsd:kern_assert+0x65 sys/arch/amd64/amd64/db_disasm.c:1074
[ 1.7136958] uvm_km_pgremove_intrsafe() at netbsd:uvm_km_pgremove_intrsafe+0x431 sys/uvm/uvm_km.c:514
[ 1.7436987] uvm_km_kmem_free() at netbsd:uvm_km_kmem_free+0x58 sys/uvm/uvm_km.c:885
[ 1.7636973] kmem_intr_free() at netbsd:kmem_intr_free+0x2d9 sys/kern/subr_kmem.c:279
[ 1.7936972] scsi_probe_bus() at netbsd:scsi_probe_bus+0x6e3 sys/dev/scsipi/scsiconf.c:536
[ 1.8136965] scsibus_discover_thread() at netbsd:scsibus_discover_thread+0x110 scsibus_config sys/dev/scsipi/scsiconf.c:325 [inline]
[ 1.8136965] scsibus_discover_thread() at netbsd:scsibus_discover_thread+0x110 sys/dev/scsipi/scsiconf.c:290
[ 1.8237103] cpu0: End traceback...
[ 1.8345971] fatal breakpoint trap in supervisor mode
[ 1.8345971] trap type 1 code 0 rip 0xffffffff80221a95 cs 0x8 rflags 0x246 cr2 0 ilevel 0 rsp 0xffff9400af979bf0
[ 1.8496729] curlwp 0xffff84ff4713d6c0 pid 0.30 lowest kstack 0xffff9400af9752c0
Stopped in pid 0.30 (system) at netbsd:breakpoint+0x5: leave
breakpoint() at netbsd:breakpoint+0x5
db_panic() at netbsd:db_panic+0xec sys/ddb/db_panic.c:69
vpanic() at netbsd:vpanic+0x2d0 sys/kern/subr_prf.c:290
kern_assert() at netbsd:kern_assert+0x65 sys/arch/amd64/amd64/db_disasm.c:1074
uvm_km_pgremove_intrsafe() at netbsd:uvm_km_pgremove_intrsafe+0x431 sys/uvm/uvm_km.c:514
uvm_km_kmem_free() at netbsd:uvm_km_kmem_free+0x58 sys/uvm/uvm_km.c:885
kmem_intr_free() at netbsd:kmem_intr_free+0x2d9 sys/kern/subr_kmem.c:279
scsi_probe_bus() at netbsd:scsi_probe_bus+0x6e3 sys/dev/scsipi/scsiconf.c:536
scsibus_discover_thread() at netbsd:scsibus_discover_thread+0x110 scsibus_config sys/dev/scsipi/scsiconf.c:325 [inline]
scsibus_discover_thread() at netbsd:scsibus_discover_thread+0x110 sys/dev/scsipi/scsiconf.c:290
ds 81
es 9bb0
fs 9c00
gs 10
rdi 5
rsi 0
rbp ffff9400af979bf0
rbx 1
rdx ffff84ff4713dad0
rcx ffffffff82bdc7de db_panic+0xde
rax ffffffff
r8 ffffffff84f6af80 cpu_info_primary
r9 0
--db_more--


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

syzbot

unread,
Apr 28, 2022, 1:53:19 AM4/28/22
to syzkaller-...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages