The 6.5.12 stable kernel update contains a number of important fixes across the tree.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2023-e4dfbf59b1
Please login to add feedback.
0 | 3 | Test Case kernel regression |
This update has been submitted for testing by acaringi.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Default & performance tests pass (KVM)
Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (535.113.1) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
Working for me in a VirtualBox VM.
sigh forgot karma.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
KVM
Works good for me. Ryzen 3700x, Rog Strix B550-F, nvidia 2070 from rpmfusion, Intel SSD.
This update has been submitted for stable by acaringi.
This update has been pushed to stable.
for me it's not functional.
I'm not sure what part of this kernel exactly is responsible for my problems but this version (and some earlier versions - it was a on and off while fedora 38) causes multiple programs to freeze. for now i rolled back to 6.5.10-200.fc38
some of the symptoms: - right click in firefox or any context menu or dialog makes firefox freeze and crash. repeats after killing the process and restarting firefox. if this happened once, restarting the machine is impossible. it hangs while shutdown. - qemu freezes and crashes if you start any vm. same here: if you started this once, the machine hangs while shutdown. only holding power off button after a while stops the horror.
actually i did not find any useful information in the logs. i don't get any useful error messages, only freezes.
i don't want to rule it out that it may be a hardware problem, but some kernel versions are enabling these freezes.
i'm even not sure if that's the best place for my problem, but the kernel is the only useful context i can find.
ok blame on me. looks like the issue was not kernel specific and intel speed step caused it.