The 5.16.19 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-2022-91633399ffPlease login to add feedback.
| -2 | 7 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
Default & performance tests pass (KVM)
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
Wfm (kvm)
Working in Fedora 35 in VirtualBox, regression tests pass.
Looks ok for me. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (510.60.02) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg). Regression test passed.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
no regressions noted
This update has been submitted for stable by jforbes.
works fine on my Thinkpad P1 gen3
wfm
This update has been pushed to stable.
5.16.19 brings back https://bugzilla.redhat.com/show_bug.cgi?id=1963717
The bug was fixed previously with the commit 159d8c274fd9:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=159d8c274fd9
but the commit was reverted with:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=8e5a2398e704
I don't quite understand how, nor does this seem to leave a trace I can get in /var/logs after a succesful boot into an older kernel, but this kernel 5.16.19 completely breaks the boot on Fedora 35, as it panics (or segfaults or something) immediately on boot after the grub screen, on a ThinkPad X220T with Intel Sandybridge CPU and graphics.
Booting into my previous kernel, 5.16.18-200.fc35.x86_64, works fine.