The 5.12.10 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-2021-bc2a819bc5Please 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 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
This update's test gating status has been changed to 'passed'.
All good in both tests. Tested on a bare-metal machine: Intel Core i5 9300H, 8 GB of DDR4 RAM and a GTX 1050 Max-Q 3G.
There is (still) a problem with bluetooth on a Dell XPS 9700.
This has been identified, see here: https://bugzilla.redhat.com/show_bug.cgi?id=1954465
Maybe this can be backported?
Up for a few hours now and no issues noticed..
Both the enabled tests pass OK. AMD 965, x86_64 work station, SSD's > RAID1. Plasma DE from Zawertun's COPR, X-server, nVidia GTX 650 (GK107) nVidia RPM's from RPMFusion (465.31)
Default & performance tests pass (KVM)
This update can be pushed to stable now if the maintainer wishes
@spockfish Sure, it can be backported since it is queued for upstream. As the bug was filed against bluez, and no one bothered to reassign it to kernel once it was determined that the problem was fixed there, I had no way of knowing about it. I don't get Cced on bugs for packages I don't maintain.
As to the negative karma, it is not a regression from the currently stable kernel (5.12.9). There are plenty of bugs in the kernel at any given time. Giving negative karma because your bug isn't fixed in an update is like saying everyone who is impacted by the numerous bugs this update does fix should have to wait for their fixes until your specific bug is fixed. Negative karma should be used for new regressions, not for new updates which do not happen to fix an existing bug in what is currently on stable.
Work here. intel i5-6500 with nivida gtx 1060.
Works fine. Default and performance regression tests also pass on all my systems:
i7-9700K(UHD Graphics 630): kernel regression test passed. Works fine for daily use.
@jforbes ok clear. Won't happen again. Anyways, thanks for your work!
Looks ok for me. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg). Regression test passed (paxtest, selinux-dac-controls and libhugetlbfs skipped).
Works fine on Acer Aspire V3-571 v: V2.11 CPU: Quad Core Intel Core i7-3632QM GPU: Intel 3rd Gen Core processor Graphics Controller KDE Plasma. No regressions found
Works fine on Thinkpad T14s AMD Ryzen 7 PRO 4750U with Radeon Graphics.
Default & performance regression tests PASS, libhugetlbfs & paxtest was skipped. Tested on x86_64, PRIME Z270-A, i5-7600K, 16GB DDR4, AMD RX 580 8GB (MESA 21.1.2-1) & 970 EVO M.2.
Works fine under VirtualBox
Default & performance test passed. Tested on an x86_64 tower PC with an AMD Ryzen 2700X processor and 64GB of DDR4 RAM.
Works, and passes the default test.
x86_64 and aarch64
no issues AMD Ryzen 5
This update has been submitted for stable by jforbes.
desktop is working normal with intel i7-11700 intel Graphics
This update has been pushed to stable.