I have two suggestions about how to keep - for a while - the 388 kernel.
First - Use DNF to remove the bad kernels. Then when a new one comes in
it will take one of those slots.
Second - Increase the number of installed kernels. That change is in
yum.conf.
https://linuxconfig.org/how-to-remove-old-unused-kernels-on-centos-linux
If the number is too high, you may run out of room in /boot partition.
Testing required....
==============Bill Gee
On 1/12/24 13:37, Michael B Allen wrote:> 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
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos