freebsd boot error: panic: IPI scoreboard is zero, initiator 1 target 1
2 views
Skip to first unread message
syzbot
Jan 11, 2021, 11:41:20 PM1/11/21
to syzkaller-f...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: ff1a3078 lio_listio: validate aio_lio_opcode
git tree: https://github.com/freebsd/freebsd-src.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=12ae78af500000
dashboard link: https://syzkaller.appspot.com/bug?extid=77d76784dcdcde69606a
userspace arch: i386
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+77d767...@syzkaller.appspotmail.com
panic: IPI scoreboard is zero, initiator 1 target 1
cpuid = 1
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xffffffff82f49420
vpanic() at vpanic+0x1c7/frame 0xffffffff82f49480
panic() at panic+0x43/frame 0xffffffff82f494e0
smp_targeted_tlb_shootdown() at smp_targeted_tlb_shootdown+0x75f/frame 0xffffffff82f49580
pmap_invalidate_range() at pmap_invalidate_range+0x1ce/frame 0xffffffff82f49600
vm_thread_stack_create() at vm_thread_stack_create+0x56/frame 0xffffffff82f49750
kstack_import() at kstack_import+0x7e/frame 0xffffffff82f49790
cache_alloc() at cache_alloc+0x687/frame 0xffffffff82f49820
cache_alloc_retry() at cache_alloc_retry+0x33/frame 0xffffffff82f49870
vm_thread_new() at vm_thread_new+0x73/frame 0xffffffff82f498b0
thread_alloc() at thread_alloc+0x66/frame 0xffffffff82f498f0
fork1() at fork1+0x443/frame 0xffffffff82f499c0
kproc_create() at kproc_create+0x9b/frame 0xffffffff82f49aa0
kproc_kthread_add() at kproc_kthread_add+0xf5/frame 0xffffffff82f49bc0
ktls_init() at ktls_init+0x2a2/frame 0xffffffff82f49c40
mi_startup() at mi_startup+0x3ac/frame 0xffffffff82f49cb0
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x67: movq $0,0x145901e(%rip)
db>
---
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 found the following issue on:
HEAD commit: ff1a3078 lio_listio: validate aio_lio_opcode
git tree: https://github.com/freebsd/freebsd-src.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=12ae78af500000
dashboard link: https://syzkaller.appspot.com/bug?extid=77d76784dcdcde69606a
userspace arch: i386
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+77d767...@syzkaller.appspotmail.com
panic: IPI scoreboard is zero, initiator 1 target 1
cpuid = 1
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xffffffff82f49420
vpanic() at vpanic+0x1c7/frame 0xffffffff82f49480
panic() at panic+0x43/frame 0xffffffff82f494e0
smp_targeted_tlb_shootdown() at smp_targeted_tlb_shootdown+0x75f/frame 0xffffffff82f49580
pmap_invalidate_range() at pmap_invalidate_range+0x1ce/frame 0xffffffff82f49600
vm_thread_stack_create() at vm_thread_stack_create+0x56/frame 0xffffffff82f49750
kstack_import() at kstack_import+0x7e/frame 0xffffffff82f49790
cache_alloc() at cache_alloc+0x687/frame 0xffffffff82f49820
cache_alloc_retry() at cache_alloc_retry+0x33/frame 0xffffffff82f49870
vm_thread_new() at vm_thread_new+0x73/frame 0xffffffff82f498b0
thread_alloc() at thread_alloc+0x66/frame 0xffffffff82f498f0
fork1() at fork1+0x443/frame 0xffffffff82f499c0
kproc_create() at kproc_create+0x9b/frame 0xffffffff82f49aa0
kproc_kthread_add() at kproc_kthread_add+0xf5/frame 0xffffffff82f49bc0
ktls_init() at ktls_init+0x2a2/frame 0xffffffff82f49c40
mi_startup() at mi_startup+0x3ac/frame 0xffffffff82f49cb0
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x67: movq $0,0x145901e(%rip)
db>
---
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.
Mark Johnston
Jan 12, 2021, 9:29:45 AM1/12/21
to syzbot, syzkaller-f...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages