CentOS - Jan 2024 - No suspend after update

Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and not it
won't suspend with the following error:

[   52.604998] Restarting kernel threads ... done.
[   52.605111] OOM killer enabled.
[   52.605111] Restarting tasks ... done.
[   52.606604] random: crng reseeded on system resumption
[   52.616014] thermal thermal_zone9: failed to read out thermal zone (-61)
[   52.791625] PM: suspend exit
[   52.791733] PM: suspend entry (s2idle)
[   52.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]  ? __pfx_autoremove_wake_function+0x10/0x10
[   72.805512]  ? __pfx_nfs41_callback_svc+0x10/0x10 [nfsv4]
[   72.805536]  kthread+0xdd/0x100
[   72.805538]  ? __pfx_kthread+0x10/0x10
[   72.805539]  ret_from_fork+0x29/0x50
[   72.805543]  </TASK>

Kernel:

  5.14.0-404.el9.x86_64

How do I boot the previous kernel?

Holding Shift down does nothing.

Pressing escape brings up some kind of emergency screen that has no
options other than to "Press any key to exit".

Is CentOS 9 Stream considered stable enough to use as an everyday desktop?

Mike

On Wed, Jan 10, 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 network
would sporadically fail to come up after suspend. No amount of
fiddling would restore. Only rebooting. I have not seen that behavior
with 388 either.

This would suggest an issue with networking / suspend between 388 and 391.

Q: If I update, am I going to lose kernel 388? How can I persist that
one specific kernel indefinitely and still be able to update the rest
of the system?

Mike

# grubby --info=ALL | grep ^kernel
kernel="/boot/vmlinuz-5.14.0-404.el9.x86_64"
kernel="/boot/vmlinuz-5.14.0-391.el9.x86_64"
kernel="/boot/vmlinuz-5.14.0-388.el9.x86_64"
kernel="/boot/vmlinuz-0-rescue-aaab5fbe787947ec94b3c7574b9d41e6"
# grubby --default-kernel
/boot/vmlinuz-5.14.0-388.el9.x86_64