The 5.16.20 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-a86334434bPlease login to add feedback.
| 0 | 6 | 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)
Are we also rolling out 5.17 with 5.16 being EOL now?
The 5.17.4 kernel will be the first official 5.17 update for F35 and F34. I expect it will come out early next week. There were a few issues which popped up during test week, and I believe they are worked out with the 5.17.3 build I pushed to F36, but I want to be sure. This should be the last 5.16 build unless a critical security issue is found in the next couple of days (I don't like to force a rebase as the only fix to those)
Thanks @jforbes! Appreciate the update.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
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.
WFM
This is working in a VirtualBox VM, regression tests are passing.
Both test cases pass on bare metal. Also haven't noticed any other weird behaviour.
This update has been submitted for stable by jforbes.
Regression tests pass on KVM
no regressios noted
This update has been pushed to stable.
This kernel prevents resuming from s2idle on my machine.
Machine: Dell Inspiron 5415
CPU: AMD Ryzen 7 5700U w/ Graphics
RAM: Crucial Ballistix 2x8GB at 2667 MT/s, Model BL8G32C16S4B.8FE
Specific issue: Upon entering s2idle, machine refuses to resume. Power button will not powercycle machine. Restarting machine requires what Dell calls a "hard reset"; unplugging the internal battery and draining flee power.
Reverting back to kernel-5.16.19-200.fc35 resolves this.
I had a similar issue, specifically with amdgpu, on an older kernel; however in that case, the machine would at least allow me to powercycle with the power button.
Not sure how to attach a dmesg here; however I see nothing bar it entering s2idle then fresh booting.