The 6.15.5 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-2025-985de950a7
Please log in to add feedback.
| -1 | 15 | 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'.
default & performance tests pass (KVM)
This is causing kernel-core crashes on every boot caused by the vmwgfx driver. See https://bugzilla.redhat.com/show_bug.cgi?id=2367745 from comment 1. Regression isn't new for dot 5 though. Kernel is otherwise functional and regression tests are all passing,.
This update's test gating status has been changed to 'waiting'.
Hardware
Notes
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'.
This update can be pushed to stable now if the maintainer wishes
Works great on Lenovo T480 and M715q Gen 2! LGTM! =)
Works.
no regressions noted
Fixes regression that made GhostTTY unusable.
Working fine
Works for me.
Works
AMD 5600G both tests are a PASS.
Works on a number of aarch64 devices including various rpi4/rockchip/tegra.
Regression report for kernel-6.15.5-200.fc42.x86_64 System: Fedora 42 Gnome/Wayland, AMD Ryzen 9 7900, AMD Radeon RX 7800 XT Issues with kernel-6.15.5-200.fc42.x86_64:
Screen flickering/flashing artifacts, particularly when using web browser (Vivaldi Flatpak) Flickering appears as thin horizontal bars that flash briefly on screen, especially around text/fonts on websites Problem occurs frequently when dialog boxes are open (e.g., text input fields) Similar flickering issues occur during gaming Slight general system performance degradation (not gaming-specific)
Current status: Staying on kernel-6.14.11-300.fc42.x86_64 which works perfectly without any of these issues. Previous kernels (6.15.3 and 6.15.4) also had similar problems.
@allmorninglong This is not a new regression with 6.15.5. By giving negative karma, you are saying that this update should not push even though the current stable kernel is 6.15.4. Essentially saying that no one else should get any fixes until your specific issue is fixed. Also of note, the issue you mention is believed to be a firmware issue, not a kernel issue. If you rebuild the 6.14.11 initramfs with your current linux-firmware packages installed, you could verify this and that would be rather helpful. Please back up your existing 6.14.11 initramfs before the rebuild for quick restore should this prove to be the iisue.
Works for me.. The tests pass OK.
Work Station, Asus prime mobo - AMD Ryzen5 5600g/iGPU, 400 Series Chipset, (UEFI) Secure boot, SSD's > RAID1 (ext4)
6.15.5 adds a new or modified random system freeze/spontaneous reboot not present in 6.15.4 or earlier. Unaffected by apps being open or idle on the desktop. linux-firmware is identical between both kernels, so not the trigger here. Baremetal, not VM.
6.15.5 100% chance to freeze/reboot with no consistent trigger. 6.15.4 after a reboot, the AMD/Firefox hardware acceleration freeze doesn't take effect and can be used freely. 6.14.11 stable.
Ryzen 5900X + Radeon 7900 XT
Working fine on 5600U / Vega iGPU.
LGTM @ AMD Ryzen 7 5700X + Radeon 6750XT Tests passed
@jforbes I performed the test - rebuilt the 6.14.11 initramfs with current firmware using sudo dracut -f /boot/initramfs-6.14.11-300.fc42.x86_64.img 6.14.11-300.fc42.x86_64 and rebooted.The rebuilt initramfs shows current firmware integration (size increased from 54.8MB to 55.2MB, timestamp updated to today), yet the system works flawlessly without any of the screen flickering issues reported with 6.15.x kernels.
Tests passed and works fine on AMD Ryzen 7 5800U with Vega iGPU.
@allmorninglong Thanks for testing that. Looks like it is a different issue (and that is a good thing because it is more likely to get a fix quickly.)
Ive did some more testing and cant sleep/suspend on 6.15.5-200.fc42. @ AMD Ryzen 7 5700X + Radeon 6750XT Yesterday the Suspend option at gnome was not working but i was doing some file-copies and thought it couldve been that. Today i did more testing, fresh boot -> suspend -> (pc sleeps) -> waking led him to just shutdown with no video signal, journalctl marking as success:
jul 08 12:09:09 krakatoa systemd-sleep[4443]: Successfully froze unit 'user.slice'.jul 08 12:09:09 krakatoa systemd-sleep[4443]: Performing sleep operation 'suspend'...`jul 08 12:09:44 krakatoa systemd-sleep[4443]: System returned from sleep operation 'suspend'.Please desconsider my last message. The same behaviour also started happening on previously 6.15.4 . Thanks !
Just FYI, 6.15.5 didn't help with the nouveau module not working since 6.15 (https://bugzilla.redhat.com/show_bug.cgi?id=2374827) Probably wasn't expected to, but still...
@jfoechsler the nouveau module is likely an issue with linux-firmware that should be fixed in the new version that's on it's way to testing.
Working fine with Thinkpad P1 Gen4 using
@pbrobinson Great to hear. I just tried firmware-20250708 from Koji and can indeed confirm display is back +1.
Thanks.
Seems OK here. Ryzen 3700x, Rog Strix B550-F, Nvidia graphics.
Works for me. Host: Z690 PG Velocita Kernel: Linux 6.15.5-200.fc42.x86_64 Display (DEL4239): 2560x1440 @ 165 Hz in 27" [External] Display (DELL U2412M): 1920x1200 @ 60 Hz in 24" [External] * CPU: 13th Gen Intel(R) Core(TM) i5-13400F (16) @ 4.60 GHz GPU: NVIDIA GeForce RTX 4070 Ti SUPER [Discrete]
Default test suite passed. (AMD Ryzen 4500U - iGPU (Vega 6).
works
Works for me on Framework 13, AMD Ryzen 5 7640U w/ Radeon 760M Graphics
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
Lenovo P16s Gen2 AMD (7840U + 780M) : everything is working fine. Tests run and uploaded (kernel-test-1752228654)
I'm happy to report that this is the first kernel in over two years that works reliably on the
Lenovo P14s Gen 4 (AMD), even with multiple USB-C docking and suspend/resume cycles. So far, it has been stable for multiple days, with no crashes, despite frequent docking, undocking, suspending, and resuming.To achieve proper 90Hz panel refresh and avoid resume issues (related to Panel Self Refresh / PSR), the following kernel parameter must be set:
Add this to
GRUB_CMDLINE_LINUXin/etc/default/grub, then regenerate the GRUB config and reboot.'Thank you' to everyone involved <3
Looks like I praised the kernel a bit too early...
Just today, my Lenovo P14s Gen 4 (AMD) failed to enter suspend and then failed to resume properly upon opening the lid. The system hung and required a force reboot.
After rebooting, I noticed the LUKS password prompt was invisible — I could still type in the passphrase blindly to boot, but nothing was displayed on screen.
So the instability saga continues — this kernel is still not reliable.
From the journal:
Still, the system is unreliable with suspend/resume. Hopefully this is helpful for anyone else testing on similar hardware.
Works on my Thinkpad Edge
no detect mt7922 Bluetooth, only Wi-Fi update all packages from cmd via dnf, same result :(
[ 6.686552] Bluetooth: Core ver 2.22 [ 6.686566] NET: Registered PF_BLUETOOTH protocol family [ 6.686567] Bluetooth: HCI device and connection manager initialized [ 6.686569] Bluetooth: HCI socket layer initialized [ 6.686571] Bluetooth: L2CAP socket layer initialized [ 6.686575] Bluetooth: SCO socket layer initialized [ 6.774547] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20250523103438 [ 8.761612] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 8.761615] Bluetooth: BNEP filters: protocol multicast [ 8.761618] Bluetooth: BNEP socket layer initialized [ 17.166752] Bluetooth: hci0: Execution of wmt command timed out [ 17.166756] Bluetooth: hci0: Failed to send wmt patch dwnld (-110) [ 17.166771] Bluetooth: hci0: Failed to set up firmware (-110) [ 17.166773] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.