syzbot
panic: Sentry detected 12 stuck task(s):
Status:
closed as dup on 2020/09/13 08:12
Reported-by: syzbot+191b0a141e02768bc48f@syzkaller.appspotmail.com
First crash: 2294d, last: 2194d
Sample crash report:
panic: Sentry detected 12 stuck task(s):
Task tid: 20589 (0x506d), entered RunSys state 3m32.92s ago.
Task tid: 19459 (0x4c03), entered RunSys state 3m32.79s ago.
Task tid: 20593 (0x5071), entered RunSys state 3m32.95s ago.
Task tid: 20586 (0x506a), entered RunSys state 3m32.92s ago.
Task tid: 31 (0x1f), entered RunSys state 3m28.35s ago.
Task tid: 20591 (0x506f), entered RunSys state 3m32.91s ago.
Task tid: 20590 (0x506e), entered RunSys state 3m30.38s ago.
Task tid: 20587 (0x506b), entered RunSys state 3m32.72s ago.
Task tid: 48 (0x30), entered RunSys state 3m32.95s ago.
Task tid: 20592 (0x5070), entered RunSys state 3m32.72s ago.
Task tid: 36 (0x24), entered RunSys state 3m31.16s ago.
Task tid: 14 (0xe), entered RunSys state 3m32.79s 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.