The 7.1.5-101/201 stable kernel updates contain 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-51abe8aeaaPlease log in to add feedback.
| 0 | 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'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
All kernels starting with 7.1.4 inclusive cannot boot on Denverton: https://bugzilla.redhat.com/show_bug.cgi?id=2508154
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
That would not be a regression from what is a currently stable kernel then. Negative karma shouldn't be because your bug has not been fixed, it is there to notify of a new regression. We don't hold back fixes for other users just because every single bug is not fixed or no kernel would ever ship.
The bug has just been filed by me and there is no mention of it anywhere else. It is a NEW regression.
If I would've detected it at 7.1.4, when it first appeared, I would've filed it then as a new regression but unfortunately the first time I detected it was 7.1.5-200 when the gateway utilizing it rebooted.
If it was in 7.1.4, it is not a new regression, it was new in 7.1.4. Currently 7.1.5-200 is the stable kernel update. Negative karma here gives the message that even though your bug is broken in the current stable kernel, no one should get the fixes that are included here because your bug isn't fixed. Stopping this kernel from shipping doesn't remove your bug from the kernel currently out there, or stop anyone who might experience a similar bug from getting the update that introduces it.
So, just for clarification for the future, it's only a regression if it was detected and reported in the first version it ever occurred even if the detection wasn't reported until a couple of versions later due to things taking time to troubleshoot and file?
This update is NOT "generally functional" on all Danverton machines.
That is correct, because as I said, anyone updating to the kernel currently on stable with your hardware will also hit that bug. Karma is a tool to help stop a regression from getting out there, but once the regression is already out there all negative karma can do is stop a new kernel from getting out there. If a kernel fixes bugs for hundreds of users, but doesn't fix your particular bug, we don't make those hundreds of users wait for their ready fixes. Filing the bug was the correct thing to do in this regard.
Ok understood, thank you.
Amd ryzen 7
Working as a VirtualBox guest and on native h/w, tests passing.
Dell Precision T5610 2 x Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz (8 cores total) NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
Works for me, the default regression tests pass.
Work Station, Asus prime mobo - Ryzen5 5600g/iGPU, 400 Series Chipset, 32 GiB RAM. (UEFI) Secure boot, 2x SSD's > RAID (ext4)
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
no regression since 7.1.4-202, r5 8400f, rx9600xt, mtk7922(wifi/bt), secureboot everything works (silverblue)
This update has been submitted for stable by jforbes.
Work as intended
Works
AMD 5600G
PASS
Works great! LGTM! =)
This update has been pushed to stable.
Lenovo P16s Gen2 AMD (7840U + 780M) : everything is working fine. Tests run and uploaded.
Looks good here. Ryzen 7800x3d, Asus TUF B650E-E, Nvidia from rpmfusion w/amdgpu enabled.
AMD Ryzen AI 9 HX 370 w/ Radeon 890M, NVIDIA Corporation AD107M [GeForce RTX 4060 Max-Q / Mobile], nouveau