The 6.16.2 stable kernel rebase contains new features, enhanced hardware support, and a number of important fixes across the tree. The 6.16.3 update contains a small set of fixes for ext4 users.
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-26fab8c58e
Please log in to add feedback.
| -1 | 18 | 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 'waiting'.
default & performance tests pass (KVM)
This update's test gating status has been changed to 'passed'.
using 6.16.1 for some time now w/o issues, expect the same for this one, but now got a /boot full warning (99%). any explenation why initramfs images are so much bigger for 6.16 kernels?
This is already using strict hostonly_mode after dracut-107 almost doubled the initramfs file size as well with sloppy hostonly_mode !
note: rescue image is for kernel 6.15.10
This kernel still has the issue introduced in 6.16.0 release candidate as described here:
https://bugzilla.redhat.com/show_bug.cgi?id=2386657
It impacts anyone using VirtualBox and almost certainly VMWare also. It isn't a new issue so no negative karma but as this is landing in a release version of Fedora I think it's a problem now. The 6.17 kernel has the same issue in both Rawhide and the 43 beta branch.
There may be a connection to the issue described in this next bug from comment 1 onward, that also involves the vmwgfx driver. This issue does impact VMWare users as well as VirtualBox users:
https://bugzilla.redhat.com/show_bug.cgi?id=2367745
Works
Noticed the same thing as @anotheruser with the initramfs ballooning in size on a couple of my systems with the 4.16 kernels, but not on another. Everything seems to be working fine though.
For the initramfs size, I haven't done a compare, but I would likely suggest the more recent linux-firmware. A firmware update doesn't rebuild the initramfs, but when you install a new kernel the initramfs is built with the current firmwares on the system. Lately we have had a nasty trend of firmwares growing massively. You can use lsinitrd on various ones and compare.
@nixuser if those 2 are in fact related, it means the bug was backported to 6.15.x stable kernels at some point as well, and is already in a release version of Fedora.
Works
@jforbes it's not the firmware ( host with nvidia + intel iGPU ) dracut 107-2:
downgraded dracut to version 105-3 ( striking difference in sloppy mode between 105 and 107 )
haven't checked lsinitrd yet.
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)
looks solid. So far, the 6.16 kernels seem to reliably suspend the system with an NVIDIA GPU [s2idle ]. This was not the case with previous kernel versions.
I haven't installed 6.16 yet, but on my F43 KVM guest, which has 6.17, the initramfs appears roughly the same size as the 6.15.9 and 6.15.10 initramfs on my F42 host - a bit smaller, in fact. The firmware on both the host and guest is dated 20250808.
Working fine
Suspension working
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
I can't boot in hp prodesk 600 g1 sff with a i7-4770.
Works for me. Two laptops. One also has an increase in initramfs: 95M /boot/initramfs-6.15.10-200.fc42.x86_64.img 95M /boot/initramfs-6.15.9-201.fc42.x86_64.img 158M /boot/initramfs-6.16.2-200.fc42.x86_64.img the other not: 60M /boot/initramfs-6.15.10-200.fc42.x86_64.img 60M /boot/initramfs-6.15.9-201.fc42.x86_64.img 61M /boot/initramfs-6.16.2-200.fc42.x86_64.img
quick update: the updated nouveau driver supports Hopper/Blackwell GPUs and adds the GSP 570 FW files to the initramfs. These were added to nvidia-gpu-firmware in June 2025, but were not used with older kernel versions. Currently, FW versions 535 and 570 can be found in the initramfs image.
Hello everyone. I installed kernel 6.16.2 using the instructions provided. Intel NUC 12 Pro (i5 1240P), Intel AX2116E WiFi HP ProBook 4540s Intel i5 3210M, Qualcomm Atheros QCA9565 WiFi I haven't tested it, but I've had it running for several hours without any problems. They seem truly excellent. Fedora 42 workstation.
I've tested it on AMD 9950X3D + 5070 TI and AMD 5900X + AMD 9070 XT and I've found no issues.
6.16.2-200.fc42.x86_64works fine on AMD Ryzen 6850U (no external modules, with only default Fedora repos enabled exceptmesa-vdpau-drivers-freeworldandmesa-va-drivers-freeworldfrom rpmfusion, Fedora KDE Spin with SELinux confined user accounts).The same for
6.16.1-200.fc42.x86_64, which I was using in the recent days on the same hardware.Works
Test was a PASS
More info about my system.
First I' had installed kernel 6.15.10-200, and got several erros about nouveau bugs in dmesg.
Second i've tried kernel 6.16.2.200 . and got the messg "BUG: unable to handle pagefault..."
my specs: OS: Fedora Kernel: x86_64 Linux 6.15.9-201.fc42.x86_64 Uptime: 8m Packages: 2233 Shell: pkcommand-not-found Resolution: 1920x1080 DE: GNOME 48.3 WM: Mutter WM Theme: Adwaita GTK Theme: Adwaita [GTK2/3] Icon Theme: Adwaita Font: Adwaita Sans 11 Disk: 563G / 933G (64%) CPU: Intel Core i7-4770 @ 8x 3.9GHz [43.0°C] GPU: Mesa Intel(R) HD Graphics 4600 (HSW GT2) GPU2: NV134 (Tesla P4) RAM: 2914MiB / 31789MiB
Very high TDP for the AMD RX 7800 XT GPU. On kernel 6.15.10, it's idle, around 7W in Gnome, and constantly 30W on this kernel.
Works great on a bunch of aarch64 devices, some KVM x86 VMs
Works great on Lenovo M715q Gen 2! LGTM! =)
Works fine on multiple servers, desktops and laptops
But perhaps, skip this one and do 6.16.3 instead due to the ext4 fixes.
no regressions noted
I am fine OS: Fedora Linux 42 (Workstation Edition) x86_64 Host: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC (SBKPF,SBKPFV2) Kernel: Linux 6.16.2-200.fc42.x86_64 Uptime: 9 mins Packages: 3011 (rpm), 15 (flatpak-system), 20 (flatpak-user) Shell: bash 5.2.37 Display (GIGA-BYTE TECHNOLOGY CO., LTD. 32"): 3840x2160 @ 120 Hz (as 2560x1440) in 32" [External] Display (AUO6DA8): 2560x1600 @ 120 Hz (as 1704x1065) in 14" [Built-in] * DE: GNOME 48.4 WM: Mutter (Wayland) WM Theme: Adwaita Theme: Adwaita [GTK2/3/4] Icons: Adwaita [GTK2/3/4] Font: Adwaita Sans (11pt) [GTK2/3/4] Cursor: default (24px) Terminal: Ptyxis 48.5 Terminal Font: Adwaita Mono (11pt) CPU: AMD Ryzen 7 PRO 7840HS (16) @ 5.14 GHz GPU: AMD Radeon 780M Graphics [Integrated] Memory: 12.24 GiB / 54.69 GiB (22%)
Noticeable enhancement. Ryzen 3700x, Rog Strix B550-F, Nvidia from rpmfusion. 6.16.3 works good, too. Thank you.
jforbes edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jforbes.
It seems USB Ethernet or related not working properly. Works with 6.15.10.
Works for me.. The tests pass OK.
crashes here
see BZ https://bugzilla.redhat.com/show_bug.cgi?id=2390635
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Running fine on my system, tests pass OK
Ryzen 9900x & 4080S
Works for me.
Problem with large initramfs still on one laptop (of two).
.3 works too.
Works fine for me on silverblue
Works for me, tests pass OK on Xeon W-2225 + Arc A380
6.16.3-200.fc42.x86_64 works fine on AMD Ryzen 6850U (no external modules, with only default Fedora repos enabled except mesa-vdpau-drivers-freeworld and mesa-va-drivers-freeworld from rpmfusion, Fedora KDE Spin with SELinux confined user accounts). I use 6.16.3 already since yesterday, no issues :) I didn't experience issues on 6.16.2 either, but I have only /boot with ext4, so I assume it was unlikely to experience issues.
Pass from me on ThinkPad E14 Gen 4
Works great.
6.16.3-200.fc42.x86_64 os ok too
Pass for me on 6.16.3-200.fc42.x86_64 on a Framework 13 running an AMD Ryzen AI 300 chip. Works well.
It seems to me that AMD #4141 has been finally resolved in Fedora as I didn't experience the issue since I moved to 6.16.X (quite a while now, since 6.16.0), though it seems users from other distributions still experience the issue. If someone else who experienced AMD#4141 still experiences it on Fedora with 6.16.X, feel free to let us know, just to see if my experience is representative (I will ask later also in the Discourse topic once 6.16.X is in stable)
The kernel works fine on Thinkpad P1 Gen4 (Intel), but on my older upgraded desktop, the default 500MB /boot can no longer fit 3 kernels + 1 kernel to installed as an update (before the oldest one is removed).
@js314592 a number of different USB ethernet adapters are working for me across a number of devices, you'll likely need to be more specific
test suite performed
Works
AMD 5600G
PASS
Works on a bunch of aarch64 and x86 devices.
Works normally, however severe CPU hogging when VMs are started (KVM/libvirt) The perf results logged are satisfactory >30%. Did not see such high values on "swapper" when rebooted back into
6.15.10-200.fc42.x86_64Perf log for
6.16.3-200.fc42.x86_64: Samples: 5K of event 'cpu_core/cycles/P', Event count (approx.): 1028190766 Children Self Command Shared Object Symbol + 36.18% 0.00% swapper [kernel.kallsyms] [k] common_startup_64 + 36.18% 0.01% swapper [kernel.kallsyms] [k] cpu_startup_entry + 36.17% 0.06% swapper [kernel.kallsyms] [k] do_idle + 30.28% 0.00% swapper [kernel.kallsyms] [k] start_secondary + 28.54% 0.11% swapper [kernel.kallsyms] [k] cpuidle_idle_call + 25.20% 0.05% swapper [kernel.kallsyms] [k] cpuidle_enter + 25.16% 0.93% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 13.49% 0.09% swapper [kernel.kallsyms] [k] asm_sysvec_apic_timer_interrupt + 12.68% 0.16% swapper [kernel.kallsyms] [k] sysvec_apic_timer_interruptPerf Log for
6.15.10-200.fc42.x86_64: Samples: 140K of event 'cpu_atom/cycles/P', Event count (approx.): 36035876715 Children Self Command Shared Object Symbol + 17.56% 0.00% swapper [kernel.kallsyms] [k] common_startup_64 + 17.56% 0.00% swapper [kernel.kallsyms] [k] start_secondary + 17.56% 0.03% swapper [kernel.kallsyms] [k] cpu_startup_entry + 17.53% 0.12% swapper [kernel.kallsyms] [k] do_idle + 12.69% 0.09% swapper [kernel.kallsyms] [k] cpuidle_idle_call + 11.31% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter + 11.29% 0.36% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 7.94% 0.00% CPU 1/KVM libc.so.6 [.] __clone + 7.94% 0.00% CPU 1/KVM qemu-system-x86_64 [.] kvm_cpu_exec + 7.93% 0.00% CPU 1/KVM libc.so.6 [.] ioctl + 7.93% 0.00% CPU 1/KVM qemu-system-x86_64 [.] kvm_vcpu_ioctl + 7.67% 0.00% CPU 2/KVM libc.so.6 [.] __clonework great on this.
Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.16.3-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 64 GiB of RAM (62.4 GiB usable) Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: ASUS
On my Thinkpad X220, about 2 minutes after boot, Wi-Fi fails with the following message in
dmesg:Followed shortly by:
The core which observed the fault gets pegged at 100% usage. The Wi-Fi card becomes unusable, trying to restart a few times and failing each time. Trying to shutdown the computer, systemd says it reached
shutdown.target, but then the procedure gets stuck with the following message:This gets repeated a few times. Shortly after reaching 130k jiffies, I started smelling burnt plastic and removed the battery.
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
Dell XPS 17 9700 won't boot. With or w/o nvidia drivers. Screen bugs out while entering LUKS password (with/without plymouth).
P.S. everything works as a charm on
6.15.10-200.fc42.x86_64Lenovo P16s Gen2 AMD (7840U + 780M) : everything is working fine. Tests run and uploaded (kernel-test-1756596004)
Boot hangs kernel panic on admittedly an old HP Z230 Tower Workstation with Intel(R) Core(TM) i7-4790 CPU. Any suggestion on how to debug? I have a few screenshots from when it hangs. No problem with previous kernel 6.15.10-200.fc42.x86_64
Timblundell: log?
Hello, there is a bug in the kernel module intel_oc_wdt causing a kernel panic in my i7-4470 cpu.
Adding modprobe.blacklist=intel_oc_wdt to grub, solves that problem.
https://bbs.archlinux.org/viewtopic.php?id=307709
After some messing about regenerating initramfs, I managed to boot into latest kernel, albeit with some bugs in the kernel log (journalctl -k). I will try the solution proposed by mwprado. Thanks! Sep 04 15:01:40 makena kernel: BUG: unable to handle page fault for address: ffffffffc07502c0 Sep 04 15:01:40 makena kernel: #PF: supervisor write access in kernel mode Sep 04 15:01:40 makena kernel: #PF: error_code(0x0003) - permissions violation Sep 04 15:01:40 makena kernel: PGD 6ad831067 P4D 6ad831067 PUD 6ad833067 PMD 105f23067 PTE 80000001096c4021 Sep 04 15:01:40 makena kernel: Oops: Oops: 0003 [#1] SMP PTI Sep 04 15:01:40 makena kernel: CPU: 0 UID: 0 PID: 569 Comm: (udev-worker) Not tainted 6.16.3-200.fc42.x86_64 #1 PREEMPT(lazy) Sep 04 15:01:40 makena kernel: Hardware name: Hewlett-Packard HP Z230 Tower Workstation/1905, BIOS L51 v01.51 04/13/2015 Sep 04 15:01:40 makena kernel: RIP: 0010:intel_oc_wdt_probe.cold+0x1e/0x7f [intel_oc_wdt] Sep 04 15:01:40 makena kernel: Code: c3 cc cc cc cc b8 f4 ff ff ff eb ec 89 c2 48 8b 7b 08 89 44 24 04 48 c7 c6 98 00 75 c0 81 e2 ff 03 00 00 c6 05 d1 33 2a 00 01 <c7> 05 07 50 2a 00 00 81 00 00 83 c2 01 89 53 34 e8 1c 50 df ed 48 Sep 04 15:01:40 makena kernel: RSP: 0018:ffffd04580b979f0 EFLAGS: 00010206 Sep 04 15:01:40 makena kernel: RAX: 00000000ffffffff RBX: ffff8d184030ab28 RCX: ffff8d1842419e40 Sep 04 15:01:40 makena kernel: RDX: 00000000000003ff RSI: ffffffffc0750098 RDI: ffff8d184248b810 Sep 04 15:01:40 makena kernel: RBP: ffff8d184248b810 R08: ffff8d184030ab28 R09: ffff8d1841117230 Sep 04 15:01:40 makena kernel: R10: ffff8d184248b810 R11: 00000000ffffffff R12: ffff8d184248b800 Sep 04 15:01:40 makena kernel: R13: ffffffffc074e068 R14: 00007fa22e517965 R15: 0000000000000000 Sep 04 15:01:40 makena kernel: FS: 00007fa22f1a63c0(0000) GS:ffff8d1f9d25f000(0000) knlGS:0000000000000000 Sep 04 15:01:40 makena kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 04 15:01:40 makena kernel: CR2: ffffffffc07502c0 CR3: 000000010ea6a006 CR4: 00000000001706f0 Sep 04 15:01:40 makena kernel: Call Trace: Sep 04 15:01:40 makena kernel: <TASK> Sep 04 15:01:40 makena kernel: platform_probe+0x46/0xb0 Sep 04 15:01:40 makena kernel: really_probe+0xde/0x340 Sep 04 15:01:40 makena kernel: ? pm_runtime_barrier+0x55/0x90 Sep 04 15:01:40 makena kernel: __driver_probe_device+0x78/0x140 Sep 04 15:01:40 makena kernel: driver_probe_device+0x1f/0xa0 Sep 04 15:01:40 makena kernel: ? __pfxdriverattach+0x10/0x10 Sep 04 15:01:40 makena kernel: driver_attach+0xcb/0x1e0 Sep 04 15:01:40 makena kernel: bus_for_each_dev+0x85/0xd0 Sep 04 15:01:40 makena kernel: bus_add_driver+0x12f/0x210 Sep 04 15:01:40 makena kernel: ? __pfx_intel_oc_wdt_platform_driver_init+0x10/0x10 [intel_oc_wdt] Sep 04 15:01:40 makena kernel: driver_register+0x75/0xe0 Sep 04 15:01:40 makena kernel: do_one_initcall+0x5b/0x300 Sep 04 15:01:40 makena kernel: do_init_module+0x84/0x280 Sep 04 15:01:40 makena kernel: init_module_from_file+0x8a/0xe0 Sep 04 15:01:40 makena kernel: idempotent_init_module+0x114/0x310 Sep 04 15:01:40 makena kernel: __x64_sys_finit_module+0x6d/0xd0 Sep 04 15:01:40 makena kernel: ? syscall_trace_enter+0x8d/0x1f0 Sep 04 15:01:40 makena kernel: do_syscall_64+0x82/0x2c0 Sep 04 15:01:40 makena kernel: ? vfs_read+0x165/0x390 Sep 04 15:01:40 makena kernel: ? vfs_read+0x165/0x390 Sep 04 15:01:40 makena kernel: ? ksys_read+0x73/0xf0 Sep 04 15:01:40 makena kernel: ? do_syscall_64+0x82/0x2c0 Sep 04 15:01:40 makena kernel: ? exc_page_fault+0x74/0x180 Sep 04 15:01:40 makena kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Sep 04 15:01:40 makena kernel: RIP: 0033:0x7fa22fa650cd Sep 04 15:01:40 makena kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 03 4d 0f 00 f7 d8 64 89 01 48 Sep 04 15:01:40 makena kernel: RSP: 002b:00007ffcc9079318 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 Sep 04 15:01:40 makena kernel: RAX: ffffffffffffffda RBX: 00005642ff443900 RCX: 00007fa22fa650cd Sep 04 15:01:40 makena kernel: RDX: 0000000000000004 RSI: 00007fa22e517965 RDI: 0000000000000013 Sep 04 15:01:40 makena kernel: RBP: 00007ffcc90793d0 R08: 0000000000000000 R09: 00007ffcc9079380 Sep 04 15:01:40 makena kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000020000 Sep 04 15:01:40 makena kernel: R13: 00005642ff43bcd0 R14: 00007fa22e517965 R15: 0000000000000000 Sep 04 15:01:40 makena kernel: </TASK> Sep 04 15:01:40 makena kernel: Modules linked in: intel_oc_wdt(+) cec wmi tpm_infineon uas usb_storage sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi scsi_dh_rdac scsi_dh_emc scsi_dh_alua i2c_dev fuse dm_multipath nfnetlink Sep 04 15:01:40 makena kernel: CR2: ffffffffc07502c0 Sep 04 15:01:40 makena kernel: ---[ end trace 0000000000000000 ]--- Sep 04 15:01:40 makena kernel: RIP: 0010:intel_oc_wdt_probe.cold+0x1e/0x7f [intel_oc_wdt] Sep 04 15:01:40 makena kernel: Code: c3 cc cc cc cc b8 f4 ff ff ff eb ec 89 c2 48 8b 7b 08 89 44 24 04 48 c7 c6 98 00 75 c0 81 e2 ff 03 00 00 c6 05 d1 33 2a 00 01 <c7> 05 07 50 2a 00 00 81 00 00 83 c2 01 89 53 34 e8 1c 50 df ed 48 Sep 04 15:01:40 makena kernel: RSP: 0018:ffffd04580b979f0 EFLAGS: 00010206 Sep 04 15:01:40 makena kernel: RAX: 00000000ffffffff RBX: ffff8d184030ab28 RCX: ffff8d1842419e40 Sep 04 15:01:40 makena kernel: RDX: 00000000000003ff RSI: ffffffffc0750098 RDI: ffff8d184248b810 Sep 04 15:01:40 makena kernel: RBP: ffff8d184248b810 R08: ffff8d184030ab28 R09: ffff8d1841117230 Sep 04 15:01:40 makena kernel: R10: ffff8d184248b810 R11: 00000000ffffffff R12: ffff8d184248b800 Sep 04 15:01:40 makena kernel: R13: ffffffffc074e068 R14: 00007fa22e517965 R15: 0000000000000000 Sep 04 15:01:40 makena kernel: FS: 00007fa22f1a63c0(0000) GS:ffff8d1f9d25f000(0000) knlGS:0000000000000000 Sep 04 15:01:40 makena kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 04 15:01:40 makena kernel: CR2: ffffffffc07502c0 CR3: 000000010ea6a006 CR4: 00000000001706f0 Sep 04 15:01:40 makena kernel: note: (udev-worker)[569] exited with irqs disabled Sep 04 15:01:40 makena kernel: e1000e: Intel(R) PRO/1000 Network Driver Sep 04 15:01:40 makena kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. ```
Sorry for the last message!
Please file a new bug in https://bugzilla.redhat.com against kernel, and all logs and debugging can occur there. Just add -1 karma and a bug link here. This is not the right place for debugging, especially if you want your problem to have at least a slight chance of resolving. Thanks.
I might also suggest trying the 6.16.5 update in updates-testing. This update is 2 kernels ago, and there have been many fixes since. And I am not sure that -1 karma on a kernel that was stable and has already been obsoleted makes much difference, though that is certainly the thing to do on a kernel that is in testing when the regression is new.