The 5.18.15 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-459818f66bPlease login to add feedback.
| 0 | 16 | 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 'failed'.
Kernel installed from koji. Seems to work fine on bare-metal Z77, 3770K, RX570 with UEFI. No issues to report so far and kernel regression tests both PASS.
Works on Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000. Passed all kernel regression tests. wi-fi: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1
This update's test gating status has been changed to 'passed'.
Runs a while and looks ok for me. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (515.57) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg). Regression test passed.
Works for me.. The enabled Default and Performance tests pass OK.
AMD 965, x86_64 Work Station (legacy BIOS) SSD's > RAID1. Plasma DE from Zawertun's COPR. nVidia GT1030 card using nVidia RPM's from RPMFusion (515.57)
Dell XPS 13 9350, Intel Core i7-6560U CPU @ 2.20GHz × 4, Mesa Intel Iris Graphics 540 (SKL GT3). Passed both regression tests. Seems fine.
Working OK here, regression tests passing.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
Works for me: all using the Mate Desktop Environment.
sirius: desktop 16GB Intel i7-3770 CPU desktop (SSD + 5 hard drives in RAID-6) real:10m20.908s user:4m38.246s sys:5m9.908sSSD only) real:
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) rea1:19m28.947s user:9m38.675s sys:7m53.892s
Works for me.
XPS 17 9700, Intel i9-10885H (16) @ 5.300GHz, Intel CometLake-H GT2 [UHD Graphics], NVIDIA GeForce RTX 2060 Max-Q.
Default & performance tests pass (KVM)
i7-9700K(UHD Graphics 630): kernel regression test passed. Works fine for daily use.
Default & performance tests pass
works!
Boot hangs at what appears to be the end of detection of USB devices. Need to CTRL-ALT-DEL and select previous kernel.
Works fine in VirtualBox
Kernel issue I report also encountered in Arch: https://bbs.archlinux.org/viewtopic.php?id=278535
Hangs on boot just as kernel-5.18.13-200.fc36 reported https://bugzilla.redhat.com/show_bug.cgi?id=2111555
Setting spectre_v2=off or retbleed=off as detailed in the Arch thread do not seem to help.
works
works for me
works for me
This update has been submitted for stable by jforbes.
I don't quite understand what the point is with pushing to stable a well documented hang situation for AMD users when the issue appears to be fixed with the 5.18.16 update that is now in testing. What's the upside? Seems like you're potentially affecting a large number of users for nothing.
So you are saying that this AMD issue is new with our 5.18.15 kernel and did not appear before then? I was under the impression that it came in with the 5.18.14 stable kernel (retbleed mitigation), and Fedora specifically has been shipping those patches since 5.18.12. Also, it is not exactly a large number of users, but enough to form a simple pattern. My reasoning was this, there are a number of valid fixes in 5.18.15, and as far as I am aware, no actual regressions compared to the Fedora 5.18.13 kernel we are currently shipping.
Well, AFAIK Fedora didn't build the 5.18.14 kernel - I looked in koji and didn't see it - so for Fedora users, the issue I'm talking about was introduced with the 5.18.15 update. My point was simply that the issue is fixed in 5.18.16 - which you've built in koji and I'm currently running. Since 5.18.16 is already in the pipeline, what's the rush with pushing 5.18.15 to stable when the impact for AMD users is potentially severe. We're talking a few extra days for 5.18.16 to clear. IMHO the risk benefit isn't worth it - but hey, it's your rodeo. ;-)
Fedora did not build the 5.18.14 kernel because every single patch (other than the version bump itself) was included in the Fedora 5.18.13 build and there were only 2 or 3 of those patches which were not included in our 5.18.12 build. We shipped retbleed mitigations with 5.18.12, the day it went public. Upstream stable waited a bit to work out some of the issues, but yes, from a code standpoint, we did ship 5.18.14, we just called it 5.18.13, so it is not a new regression in this kernel. And I am still waiting for the f35 build of 5.18.16 to finish.
OK, I just know I was running 5.18.13 with no issues, and then got hit with the issue in 5.18.15 (which was also reported in Arch, specifically for 5.18.15 link above). So I'm certainly not the only one reporting this issue specifically for 5.18.15. I'm now running 5.18.16 and the issue is resolved.
5.18.16-200.fc36 doesn't fix my issue on a AMD Ryzen Threadripper PRO 3975WX :(
I'll update the BZ.
This update has been pushed to stable.
Doesn't boot on my machine. Just gives a text output with some generic device discovery messages. It looks like there's an error at the top, but that's scrolled offscreen within miliseconds. Never prompted for my disk encryption password so these logs are not stored either. Asus M5A97 Evo R2.0 AMD FX 6300 NVIDIA GeForce GT640
Reverting to 5.18.13 works.
@rspliet read my comments above.
@gcbox I had seen your comment and had since tested 5.18.16 successfully, thanks. That said, my feedback here is mainly meant to alert the kernel team that something is wrong and that this is not an anomaly - hence the reply with the downvote and details. 5.18.15 should not have been pushed, and I hope that my feedback can lead to the withdrawal of this kernel. If 5.18.16 hadn't worked then I would have chimed in on bugzilla too.
Well, there are two bugs for this now: https://bugzilla.redhat.com/show_bug.cgi?id=2115733 and https://bugzilla.redhat.com/show_bug.cgi?id=2115927. My conscience is clear, I did what I was supposed to do and raised the red flag. Now we are in a situation where a known serious bug has been pushed to stable. Hopefully 5.18.16 is pushed soon. The damage, unfortunately has been done.