syzbot
panic: Sentry detected 13 stuck task(s): (2)
Status:
closed as dup on 2020/09/13 08:10
Reported-by: syzbot+a38f965d28342a2ca0ba@syzkaller.appspotmail.com
First crash: 2156d, last: 2151d
Sample crash report:
panic: Sentry detected 13 stuck task(s):
Task tid: 3748 (0xea4), entered RunSys state 3m17.02s ago.
Task tid: 3746 (0xea2), entered RunSys state 3m17.01s ago.
Task tid: 9 (0x9), entered RunSys state 3m12.25s ago.
Task tid: 3742 (0xe9e), entered RunSys state 3m16.98s ago.
Task tid: 3743 (0xe9f), entered RunSys state 3m17.01s ago.
Task tid: 43 (0x2b), entered RunSys state 3m17s ago.
Task tid: 8 (0x8), entered RunSys state 3m12.25s ago.
Task tid: 6 (0x6), entered RunSys state 3m12.26s ago.
Task tid: 3750 (0xea6), entered RunSys state 3m12.25s ago.
Task tid: 2 (0x2), entered RunSys state 3m12.25s ago.
Task tid: 3744 (0xea0), entered RunSys state 3m16.98s ago.
Task tid: 3741 (0xe9d), entered RunSys state 3m17.01s ago.
Task tid: 7 (0x7), entered RunSys state 3m12.26s 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.