search for: wq_busy

....797260] Filesystems sync: 0.005 seconds [ 52.797579] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 52.799127] OOM killer disabled. [ 52.799128] Freezing remaining freezable tasks ... [ 72.805437] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 72.805450] task:NFSv4 callback state:I stack:0 pid:2191 ppid:2 flags:0x00004000 [ 72.805453] Call Trace: [ 72.805454] <TASK> [ 72.805456] __schedule+0x21b/0x550 [ 72.805463] schedule+0x2d/0x70 [ 72.805466] nfs41_callback_svc+0x186/0x190 [nfsv4] [ 72.805508]...

...2024 at 11:57?PM Michael B Allen <ioplex at gmail.com> wrote: > > Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and now it > won't suspend with the following error: ... > [ 72.805437] Freezing of tasks failed after 20.006 seconds (1 tasks > refusing to freeze, wq_busy=0): > [ 72.805450] task:NFSv4 callback state:I stack:0 pid:2191 > ppid:2 flags:0x00004000 FYI After reverting to 5.14.0-388 yesterday, stability is restored. I can consistently suspend and resume without issues. In hindsight, kernel 391 was also giving me issues. My wired netwo...

...B Allen <ioplex at gmail.com> wrote: >> >> Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and now it >> won't suspend with the following error: > ... >> [ 72.805437] Freezing of tasks failed after 20.006 seconds (1 tasks >> refusing to freeze, wq_busy=0): >> [ 72.805450] task:NFSv4 callback state:I stack:0 pid:2191 >> ppid:2 flags:0x00004000 > > FYI > > After reverting to 5.14.0-388 yesterday, stability is restored. I can > consistently suspend and resume without issues. > > In hindsight, kernel 39...