Comment # 7 on bug 1210111 from Dmitry Markov

(In reply to Takashi Iwai from comment #6)
> Thanks.  This made me wonder whether it's an issue rather in initrd.
> 
> If you have the still-working initrd for 6.2.6, back up the initrd file to
> another file in /boot, recreate 6.2.6 initrd and retest / verify whether the
> latest initrd still works.
> 
> In case it fails to boot, you can specify the backed-up initrd file in GRUB
> menu, too.

i regenerated all initrd with command

> sudo dracut -f --regenerate-all

naturally after copying the current working initrd

> [werwolf@power] ~  
> ❯ ls -lah /boot | grep initrd
> lrwxrwxrwx 1 root root   32 2023.04.14_21:03 initrd -> initrd-6.2.10-3.g0ae17b8-default
> -rw------- 1 root root  45M 2023.04.17_20:07 initrd-6.2.1-1-default
> -rw------- 1 root root  45M 2023.04.17_20:07 initrd-6.2.2-1-default
> -rw------- 1 root root  45M 2023.04.17_13:19 initrd-6.2.6-1-COPY
> -rw------- 1 root root  45M 2023.04.17_20:07 initrd-6.2.6-1-default

The timestamps on the files show that the images have been recreated.

the situation has not changed, I still boot with the 6.2.6 kernel without
problems, but I can not boot with newer kernels.