syzbot
panic: Sentry detected 11 stuck task(s):
Status:
closed as dup on 2020/09/13 08:12
Reported-by: syzbot+6db298cccd4cb320fe2b@syzkaller.appspotmail.com
First crash: 2240d, last: 2145d
Sample crash report:
panic: Sentry detected 11 stuck task(s):
Task tid: 10748 (0x29fc), entered RunSys state 3m11.82s ago.
Task tid: 10742 (0x29f6), entered RunSys state 3m11.83s ago.
Task tid: 10747 (0x29fb), entered RunSys state 3m11.84s ago.
Task tid: 10745 (0x29f9), entered RunSys state 3m11.82s ago.
Task tid: 38 (0x26), entered RunSys state 3m10.71s ago.
Task tid: 3343 (0xd0f), entered RunSys state 3m7.72s ago.
Task tid: 36 (0x24), entered RunSys state 3m11.71s ago.
Task tid: 10749 (0x29fd), entered RunSys state 3m11.83s ago.
Task tid: 10744 (0x29f8), entered RunSys state 3m11.79s ago.
Task tid: 51 (0x33), entered RunSys state 3m11.81s ago.
Task tid: 14 (0xe), entered RunSys state 3m11.71s ago.
Search for '(*Task).run(0x..., 0x<tid>)' in the stack dump to find the offending goroutine
Stack for running G's are skipped while panicking.
* Struck through repros no longer work on HEAD.