The 5.13.6 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-12618d9b08Please login to add feedback.
| 0 | 3 | 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's test gating status has been changed to 'passed'.
Default & performance tests pass (KVM)
This update has been pushed to testing.
caja-1.24.1-1.fc33.x86_64 cannot manage smartphones to transfer, copy, paste or access the device or just to view anything. I reported the bug in detail on BUGZILLA a few days ago. Otherwise everything looks fine.
Fedora 33 Mate on Acer NITRO 5 AN515-54-574Q Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz (8) @ 4.100GHz GPU: Intel UHD Graphics CoffeeLake-H GT2 [UHD Graphics 630] GPU: NVIDIA Model: TU117M GeForce GTX 1650 Mobile / Max-Q
Works well on ThinkPad P1 G2.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
This broke booting with FIPS. Just saying that this regression has been known for two months..
Over the years I've seen dozens of FIPS boot failures. Would it be possible to include this into the gating tests?
Sorry, to be honest, I didn't expect anyone was actually using fips in Fedora, the options were more about keeping things tested for RHEL. It looks like the fixes for that were done in rawhide recently, and I can bring them back for 5.13.8
@jforbes: If FIPS is not something that Fedora officially supports, I am also happy to disable our FIPS tests there, and only run them on RHEL (it also breaks there, but maybe a bit less often). Indeed there are not very many hits for "Fedora FIPS", so maybe we are being overly expectant here? (Then again, this time around it was not the cockpit team but someone else who filed the F33 bug, so at least one other person cares 😀). Thanks!
@martinpitt It is not so much a "not supports" as we do not do certification on Fedora, so the assumption was people who cared about FIPS were using RHEL. When the rawhide bug was filed, RHEL people did start working to figure out the issue, so the testing is valid because it does get a response. I just didn't think it was of value to backport the fix. Now that I know there are users, I am happy to do so.