Comment 3 for bug 1983177

I'm getting similar problem on the very same OEM kernel. Although my task is 'fstrim' in opposite to 'kernel kcompactd above:
'''
 sudo dmesg | grep -A 1 'Freezing of tasks failed'
[sudo] hasło użytkownika nusch:
[174986.443874] Freezing of tasks failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0):
[174986.444618] task:fstrim state:R running task stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175006.946133] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
[175006.946849] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175027.751755] Freezing of tasks failed after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
[175027.752504] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175048.239411] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
[175048.240147] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175069.434969] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
[175069.435472] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175090.088861] Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
[175090.089672] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
'''
Wondering if the resason of any could be state of heavy swap usage, although IMHO in such case this should we handled differently when entering suspend