The 6.19.9 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-2026-25d1b9d7f6Please log in to add feedback.
| 0 | 9 | 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 'failed'.
Working fine as a VirtualBox guest. Tests pass.
default & performance tests pass (KVM)
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Works for me, the default tests passed OK..
Work Station, Asus prime mobo - Ryzen5 5600g/iGPU, 400 Series Chipset, 32 GiB RAM. (UEFI) Secure boot, 2x SSD's > RAID1 (ext4)
Works.
suspend (s2idle) / resume ok. intel i7-1165G7 / RTX 2060 nvidia drivers 595.45.04
Looks just fine. Ryzen 7800x3d, Asus B650E-E, Nvidia from rpmfusion.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
no regressions noted
Works for me.
freeze on a bare metal boot:
AMD Ryzen AI 9 HX 370 w/ Radeon 890M
test suite performed
Works great! LGTM! =)
working well for me on framework 13 Ryzen AI 7 350. seems to have fixed the freezes i was seeing on 6.19.8 that were possibly related to amdgpu mes scheduling
6.19.9-200.fc43.x86_64works fine on Ryzen 7 PRO 6850U natively (average daily activities tested: Firefox, etc). F43 KDE SpinWorks
AMD 5600G
PASS
This update has been submitted for stable by acaringi.
FEDORA-2026-25d1b9d7f6 ejected from the push because "Cannot find relevant tag for kernel-6.19.9-200.fc43. None of ['f43-updates', 'f43-updates-pending'] are in ['epel9-next-testing', 'eln-updates-testing', 'epel8-testing', 'epel9-testing', 'f44-updates-testing', 'f45-updates-testing', 'epel10.3-testing', 'f42-flatpak-updates-testing', 'f42-updates-testing', 'epel10.1-testing', 'epel10.2-testing', 'f43-flatpak-updates-testing', 'f43-container-updates-testing', 'f43-updates-testing', 'f44-flatpak-updates-testing']."
Seem this wasn't pushed...
It was pushed, there was just some kind of blip with the update system (this isn't the only affected update):
I think somebody has since manually changed the state of affected updates to 'stable', probably by direct DB fiddling so that's why there's no message indicating it.
Yup, see it now!