syzbot


panic: No chunks on the queues for sid 5.

Status: closed as dup on 2019/03/22 15:34
Reported-by: syzbot+0a4d3d884c5160ccf5eb@syzkaller.appspotmail.com
First crash: 2030d, last: 2030d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
panic: No chunks on the queues for sid 2. 1 2032d 2032d

Sample crash report:
panic: No chunks on the queues for sid 5.
cpuid = 0
time = 382
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xfffffe0016ad96f0
vpanic() at vpanic+0x1e0/frame 0xfffffe0016ad9750
panic() at panic+0x43/frame 0xfffffe0016ad97b0
sctp_free_assoc() at sctp_free_assoc+0x32b3/frame 0xfffffe0016ad9850
sctp_timeout_handler() at sctp_timeout_handler+0x167f/frame 0xfffffe0016ad98e0
softclock_call_cc() at softclock_call_cc+0x1dd/frame 0xfffffe0016ad99b0
softclock() at softclock+0xa3/frame 0xfffffe0016ad99f0
ithread_loop() at ithread_loop+0x2f2/frame 0xfffffe0016ad9a60
fork_exit() at fork_exit+0xb0/frame 0xfffffe0016ad9ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0016ad9ab0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 12 tid 100018 ]
Stopped at      kdb_enter+0x6a: movq    $0,kdb_why

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/03/18 22:07 freebsd b24a98cb7ea8 4656beca console log report ci-freebsd-main
* Struck through repros no longer work on HEAD.