syzbot
panic: Sentry detected 10 stuck task(s):
Status:
closed as dup on 2020/09/13 08:10
Reported-by: syzbot+034d580e89ad67b8dc75@syzkaller.appspotmail.com
Fix commit:
de85b045d42f
kvm/x86: handle a case when interrupts are enabled in the kernel space
First crash: 2189d, last: 2148d
Sample crash report:
panic: Sentry detected 10 stuck task(s):
Task tid: 46 (0x2e), entered RunSys state 3m33.39s ago.
Task tid: 12 (0xc), entered RunSys state 3m33.37s ago.
Task tid: 16 (0x10), entered RunSys state 3m33.37s ago.
Task tid: 26 (0x1a), entered RunSys state 3m33.37s ago.
Task tid: 16296 (0x3fa8), entered RunSys state 3m33.39s ago.
Task tid: 16297 (0x3fa9), entered RunSys state 3m33.39s ago.
Task tid: 16291 (0x3fa3), entered RunSys state 3m33.39s ago.
Task tid: 16295 (0x3fa7), entered RunSys state 3m32.67s ago.
Task tid: 47 (0x2f), entered RunSys state 3m33.39s ago.
Task tid: 16285 (0x3f9d), entered RunSys state 3m32.67s 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.