The 5.11.7 stable kernel update contains a number if 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-bb755ed5e3
Please login to add feedback.
0 | 10 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
On my laptop this kernel is still impacted by https://bugzilla.redhat.com/show_bug.cgi?id=1936791. I was able to boot with iommu=off, but upon booting my wireless card (ath10k) was not available so I could not connect to the network (probably related to the ath10k updates in the kernel rather than iommu though, I will test the previous 5.11 kernel and find out). The next release should have the fixes required for iommu (see https://bugzilla.kernel.org/show_bug.cgi?id=212133). On the plus side, the kernel tests all passed, and the update works fine on another machine that doesn't have the same hardware. On a side note, would it be possible to have the 5.10.24 kernel build available in koji so I can have ?
This update's test gating status has been changed to 'ignored'.
correction to my previous statement, there are no ath10k updates so maybe it was something else. Anyway re: 5.10.24 I meant to write 'so i can have it to test the wireless issue'
sorry last comment: turns out if i manually enforce the
iommu=off
kernel boot flag my wifi card stops functioning. so it wasn't the 5.11.7 kernel that caused my wifi issue.This update has been pushed to testing.
for my other machine, this update works fine. re: wifi issues on my laptop, turns out that DMA on this chipset uses IOMMU, so setting
iommu=soft
in the kernel boot options allows me to boot my laptop as it pushes IOMMU handling to software instead of using hardware IOMMU.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), something isn't able to build with VirtualBox 6.1.18 from Oracle. Have to wait for a new release of VB. Works with Gnome-Desktop (Xorg). Regression test passed (paxtest, selinux-dac-controls and libhugetlbfs skipped).
This update can be pushed to stable now if the maintainer wishes
Works.
Default & performance tests pass (KVM)
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
Running the test suite resulted in PASS.
Good.
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 20.3.4-2) & 970 EVO M.2.
Appears to be working good. Not seeing any problems so far. AMD Ryzen + Nvidia.
Works fine on my Ryzen 5900X + nVidia RTX 3070 (460.56 driver from rpmfusion). As mostly every time for as long as I remember, screen output does not work after grub menu, which is solved by reboot, but that was always the case with nVidia (it's a temporary card right now). Whole 5.11.x series worked from day-1 with zero issues.
"As mostly every time for as long as I remember, screen output does not work after grub menu, which is solved by reboot, but that was always the case with nVidia (it's a temporary card right now)"
What does that mean? I don't have this problem with a 2060. It probably shouldn't be happening with a 3070 either. Might be from rpmfusion or an issue from other reasons.
Works for me..
The enabled Default and Performance 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 Negativo17 (460.56)
@soeiro that's my personal experience, I had a previous desktop with GTX1060 and every other kernel update it either fails to boot on reboot or driver is not loaded, or resolution is messed up, all kind of things. I've built a new one with AMD GPU and had no issues whatsoever as far as kernel update goes. I've put 3070 this week to test something and at first update it failed to boot into graphical target (tty was working fine). It's mostly solved by another reboot, but why is it always like that. Sorry for the spam.
Works fine on HP Laptop 15-ba069ax -- AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G (Family 15h (Models 60h-6fh)); AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]; 1866MHz 8GB single-channeled RAM (6,8GiB usable)
Running on GNOME 3.38.3, no regressions found for my use case (browsing, IM, using ntfs3 kernel module). Tainted kernel 12288
@agurenko re:
"I had a previous desktop with GTX1060 and every other kernel update it either fails to boot on reboot or driver is not loaded, or resolution is messed up, all kind of things"
I have a GTX1060 in one of my systems and have never had any of these issues you describe. Maybe it's something else causing the problem...
Works fine, kernel tests passed on Lenovo E56
I have problems with my optimus system (nvidia/intel). The nvidia (460.56) proprietary drivers provided by fedora are not yet compatible with the 5.11 kernel. A new version (440.67) of these are available : https://www.nvidia.fr/Download/driverResults.aspx/171406/fr.
Quite a crash with wayland and kde plasma
jforbes edited this update.
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
I hit the following BUG https://pastebin.com/raw/XkKSjpph Quickly found it's being discussed in linux-mm mailing list: https://www.spinics.net/lists/linux-mm/msg249401.html
Breaks the rendering of the mouse cursor on Wayland for NVIDIA GeForce Kepler-generation GPUs driven by nouveau. This is a known bug in upstream kernel 5.11+. See RHBZ #1941291 . A patch exists on the nouveau mailing list but has yet to be brought upstream. May wish to apply this downstream.
Works fine - HP (8th Gen)