The 6.3.11 stable kernel update contains a number of important fixes across the tree.
The 6.3.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-2023-2846d5650ePlease login to add feedback.
| 0 | 14 | 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 has obsoleted kernel-6.3.10-200.fc38, and has inherited its bugs and notes.
./runtests.shPASS with the kernel-6.3.11-200.fc38.x86_64 builds within a kvm/qemu VM (KDE spin, up to date with all testing repos of F38 enabled) with CPU-passthrough on a AMD Ryzen 6850 PRO host. No third party modules/software (tainted = 0).I tested the VM some minutes with average activities, works fine so far. No errors/issues when using it.
Occurrence of Fedora BZ#2193110 / kernel BZ#217528 not yet tested.
Occurrence of Fedora BZ#2218590 not yet tested.
Works fine on my Thinkpad Edge (2013)
This update's test gating status has been changed to 'passed'.
Looks OK here as both native and as a VirtualBox VM.
Intel NUC i7 NUC11PAH 1 x 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
Works well. Ryzen 3700x, Rog Strix B550-F, nvidia from rpmfusion.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
AMD Ryzen 7 PRO 5850U with Radeon Graphics
6.3.9 and 6.3.10 had significant problems for my Thinkpad T14s Gen 2 AMD. 6.3.11 seems OK.
Seems ok on AMD Ryzen 5 7600X
The 6.3.9 / 6.3.10 problem still present - just experienced a black screen, followed by a random lockup after rebooting requiring a forced reboot (power cycle).
Slimbook Titan
AMD Ryzen 9 5900HX with Radeon Graphics
Radeon Vega Series / Radeon Vega Mobile Series
GeForce RTX 3070 Mobile / Max-Q
Will test with my other AMD laptops later.
J.K.
Default & performance tests pass (KVM)
i7-9700K(UHD Graphics 630): kernel regression test passed. Works fine for daily use.
Seems to work fine on bare-metal HP Z440, AMD RX570 with UEFI. No issues to report so far and kernel regression tests both PASS.
Working fine here.
Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz
Graphics Processor: Mesa DRI Intel® HD Graphics 4000. driver: i915 v: kernel arch: Gen-7
wi-fi: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel.
Default fedora btrfs filesystem.
Suspension works
Passed all kernel regression tests
@cowboysmall Did you file a bug? -> https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=kernel&format (carefully read the template in the "description" field and provide what is asks for)
@py0xc3: https://bugzilla.redhat.com/show_bug.cgi?id=2219406
J.K.
#2216972 still present -- nftables/firewalld does not complete when using sets; unable to interact with nftables after boot up.
boot failed with MCE errors on my Dell Inspiron 3180 11"
Works great on Lenovo T480! LGTM! =)
Yeah, problem that was apparently introduced in kernel-6.3.9 still exists with certain amd graphics cards.
Exactly the same issue, total hard lockup, I cannot get anything from the logs.
Desktop Box, Ryzen5 5600g/AMDGPU 400 Series Chipset, integrated graphics.
Back to 6.3.8 as that works fine.
Works for me.
fedora test suite PASS
Is it possible that the new "linux-firmware"-package helps? It is in testing at the Moment. In the changelog is something with amd-gpu.
Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (535.54.03) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
@ibims wrote "Is it possible that the new "linux-firmware"-package helps? "
no, still a hard lockup. I was running the newer firmware before the 6.3.11 update here. I even rolled that back to test..
Default and performance pass. HP 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD 630].
@g6avk remember when rolling back or updating linux-firmare to test, it typically doesn't matter what version is on the system, it matters which firmware was on the system when the initramfs was made. So changing firmware versions doesn't make any difference unless you make a new initramfs or install a new kernel. This is also why firmware can break something, and it not show up until a week or 2 later when a kernel update ships.
I haven't seen the issues noted in the reports, this is an intel box
@g6avk What I did is made a copy of /boot/initramfs-6.3.11-200.fc38.x86_64.img before upgrading to the updates-testing firmware, installed the new firmware, then ran
dracut -fto ensure the new firmware is included in that initramfs image.It looks like there is a fix for the AMD issues, but it won't be available till 6.5. Some members of the Arch community have patched the 6.3.11 (I think) kernel and have tested it successfully:
https://gitlab.freedesktop.org/drm/amd/-/issues/2658#note_1979350
and here is the patch:
https://gitlab.freedesktop.org/agd5f/linux/-/commit/b391007884c2a4ffd7e7e1cd45de98a7e4136739
J.K.
Seems to work for me. The sporadic boot failures observed with 6.3.9 and 6.3.10 on my Ryzen 3 3200G machine have not occurred so far, but this could be mere luck as the possible root cause is not yet fixed.
Seems to work fine on bare-metal HP EliteBook 840 G6 with UEFI and SecureBoot. No issues to report so far and kernel regression tests both PASS.
@jforbes @wtogami thanks both for the advice, I've learnt something this week! I was more concerned about testing the kernel and never gave updating the initramfs a second thought. I understand now how it all works..
So does that mean that the issue is improved with updated firmware?
@jforbes No, still a hard lockup with 6.3.11 and updated firmware.
jforbes edited this update.
I was hoping to get the lockup issues resolved before pushing an update, but given the disclosure of StackRot, I am afraid we need to push to stable so that at least users who are not impacted by the lockup bug are covered.
This update has been submitted for stable by jforbes.
I just experienced BZ#2218590: the behavior is exactly the same as described for 6.3.8 and 6.3.10. But while 6.3.8 and 6.3.10 produced comparable logs, those in 6.3.11 seem to differ:
...
See also BZ#2218590
This update has been pushed to stable.
no regressions noted
Boot failed with black screen on Lenovo Thinkpad P1 gen5. (intel core i7-12800H, nvidia rtx a1000)
6.3.12 also works for me on the same Thinkpad Edge
With regards to my previous comment, 6.3.11 now produces the same logs as 6.3.8 and 6.3.10:
Extract (see BZ#2218590 for more logs):
No issues so far. I haven't seen any AMD GPU crashes on my RX 6700 (navi22).
Not Compatible with my ASUS Laptop
processor : 1 vendor_id : AuthenticAMD cpu family : 21 model : 112 model name : AMD A9-9425 RADEON R5, 5 COMPUTE CORES 2C+3G
please consider to update the issues. TQ
Getting random hard system freezes, all of them when using the graphical interface. Reverted to kernel 6.3.8; seems stable so far.
Motherboard: ASUSTeK COMPUTER INC. PRIME B450M-A UEFI version 3604 CPU: AMD Ryzen™ 5 5600G with Radeon™ Graphics × 12 iGPU: AMD Radeon™ Graphics OS: Fedora Linux 38 (Workstation Edition) 64 bits GNOME version: 44.2 Window system: Wayland
Freezes while booting on T14s G1 on AMD.