The 6.12.8 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-dbab3ac043Please login to add feedback.
| 0 | 12 | Test Case kernel regression |
This update has been submitted for testing by acaringi.
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)
Works good on my Thinkpad Edge laptop :)
Looks good here, regression tests passing.
Works for me, the enabled Default and Performance tests pass OK.
Work Station > Asus prime mobo - Ryzen5 5600g/AMDGPU 400 Series Chipset, (UEFI) Secure boot, SSD's > RAID1 (ext4)
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 PASS.
Default (libhugetlbfs, memfd & paxtest skipped) and performance tests pass; works in general.
Would be interesting to know whether folks that are having AMD GPU and are experiencing problems with recent 6.12 kernels benefit from the upcoming fix in .9: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=queue/6.12&id=e97feb2e6d667e2e4e4b5443670d112e483a3b71
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works great! LGTM! =)
kernel tests pass
Works for me.
Default test suite passed, AMD Ryzen 4500U - iGPU (Vega 6), no issues found.
crashes here (Intel Gen. 11) since 6.12.7:
https://lore.kernel.org/all/9dee19b6185d325d0e6fa5f7cbba81d007d99166.camel@sapience.com/
fix should be in 6.12.9:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/queue-6.12/tracing-have-process_string-also-allow-arrays.patch?id=edd231e77445f7293004a6059bec5717b618ce5f
I wonder where all the positiv feedbacks come from. I always do a "soundcheck" with new kernels, like:
sudo dmesg|grep -iEw 'bad|bug|conflict|corrupted|error|fail|failed|fault|fatal|invalid|Lock|NULL|segfault|stack|trace|warn'
Working fine on baremetal
kernel tests PASSED
Suspension works
It seems bug#2332388 is fixed with this kernel
no regressions noted
Just noticed and hit this: https://discussion.fedoraproject.org/t/after-upgrading-to-kernel-6-12-virtualbox-fails-to-start/139896
Is this an intentional change as it's breaking VBox run?
Seems upstream change, is there any discussion about this behaviour or how is this affecting other hypervisors. Seems quite relevant for workstation where KVM is not necessary used hypervisor.
Looks OK. Ryzen 3700x, Rog Strix B550-F, Nvidia from rpmfusion. For the last few kernels I have randomly been getting errors in dmesg regarding ee1004, but still runs OK.
Works fine on Lenovo ThinkPad P1 Gen2
Working on MSI desktop with Intel 10th Gen 7 and Nvidia RTX 3080 with proprietary drivers.
LGTM on Framework 16
Same behavior from all kernel-6.12.*-200.fc41
ASUS Zenbook S 16 UM5606WA KDE Plasma: 6.2.5 Mesa drivers: 24.3.2-2.fc41
Getting: [drm] Fence fallback timer expired on ring gfx_0.0.0
Behavior not show with 6.11.*-fc41
This update has been submitted for stable by acaringi.
This update has been pushed to stable.
I've a Raspberry Pi 4 Model B with the latest firmware up to this date and since kernel 6.11.x I've been experiencing this bug with different kernels from 6.12.x. I'm using a network drive with SMB 1.0 (old I know) but worked fine until the latest kernel 6.11.x with a few random warnings in dmesg.
Bug details from dmesg on kernel 6.12.8:
[ 897.638199] netfs: Can't donate prior to front [ 897.638238] R=00070bef[8] s=2c1000-2c3fff 0/3000/3000 [ 897.638250] folio: 2c0000-2c3fff [ 897.638254] donated: prev=0 next=0 [ 897.638258] s=2c1000 av=3000 part=3000 [ 897.638327] ------------[ cut here ]------------ [ 897.638331] kernel BUG at fs/netfs/read_collect.c:312! [ 897.638378] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP [ 897.638401] Modules linked in: binfmt_misc nls_utf8 cifs cifs_arc4 nls_ucs2_utils cifs_md4 dns_resolver netfs nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat wireguard libcurve25519_generic ip6_udp_tunnel udp_tunnel ip_set nf_tables brcmfmac_wcc btsdio bcm2835_v4l2(C) bcm2835_mmal_vchiq(C) videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 brcmfmac videodev videobuf2_common cpufreq_dt brcmutil snd_bcm2835(C) mc cfg80211 vfat fat hci_uart btqca btrtl broadcom btintel bcm_phy_ptp bcm_phy_lib btbcm raspberrypi_cpufreq bluetooth genet vchiq(C) mdio_bcm_unimac rfkill vc4 pwrseq_core snd_soc_hdmi_codec ledtrig_default_on i2c_mux_pinctrl snd_soc_core leds_gpio iproc_rng200 bcm2711_thermal snd_compress i2c_mux ac97_bus snd_pcm_dmaengine loop fuse dm_multipath nfnetlink mmc_block rpmb_core snd_pcm snd_timer snd pwrseq_simple sdhci_iproc raspberrypi_hwmon dwc2 v3d [ 897.638626] gpio_raspberrypi_exp gpu_sched pwm_bcm2835 sdhci_pltfm crct10dif_ce bcm2835_wdt soundcore sdhci drm_display_helper udc_core i2c_brcmstb clk_bcm2711_dvp cec mmc_core i2c_bcm2835 drm_dma_helper phy_generic bcm2835_dma nvmem_rmem scsi_dh_rdac scsi_dh_emc scsi_dh_alua aes_neon_bs [ 897.638917] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Tainted: G C 6.12.8-200.fc41.aarch64 #1 [ 897.638947] Tainted: [C]=CRAP [ 897.638959] Hardware name: raspberrypi,4-model-b Raspberry Pi 4 Model B Rev 1.5/Raspberry Pi 4 Model B Rev 1.5, BIOS 2023.07 07/01/2023 [ 897.638990] Workqueue: cifsiod cifs_readv_worker [cifs] [ 897.639309] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 897.639333] pc : netfs_consume_read_data.isra.0+0x95c/0xa50 [netfs] [ 897.639404] lr : netfs_consume_read_data.isra.0+0x95c/0xa50 [netfs] [ 897.639457] sp : ffff80008006bca0 [ 897.639470] x29: ffff80008006bcb0 x28: 0000000000003000 x27: 00000000002c1000 [ 897.639499] x26: ffff1f91833f7180 x25: 0000000000000000 x24: 00000000002c4000 [ 897.639526] x23: 0000000000003000 x22: ffff1f90401e4a28 x21: ffff1f91003ca580 [ 897.639554] x20: 0000000000004000 x19: ffff1f90401e4a28 x18: 0000000000000000 [ 897.639582] x17: ffff70acf0635000 x16: ffffaee50d274450 x15: c688d3fca4a43986
I also collected a few unrelated warnings in dmesg from kernel 6.11.10 which I found to be the most stable to this date:
[ 1.005371] simple-framebuffer simple-framebuffer.0: [drm] ERROR could not acquire memory range [mem 0x3e513000-0x3ebebfff flags 0x200]: -16 [ 1.005387] simple-framebuffer simple-framebuffer.0: probe with driver simple-framebuffer failed with error -16
[ 20.940450] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
[ 21.338145] Bluetooth: hci0: BCM: chip id 107 [ 21.338535] Bluetooth: hci0: BCM: features 0x2f [ 21.340164] Bluetooth: hci0: BCM4345C0 [ 21.340220] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000 [ 21.340880] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 21.340899] Bluetooth: hci0: BCM: 'brcm/BCM4345C0.raspberrypi,4-model-b.hcd' [ 21.340903] Bluetooth: hci0: BCM: 'brcm/BCM4345C0.hcd' [ 21.340907] Bluetooth: hci0: BCM: 'brcm/BCM.raspberrypi,4-model-b.hcd' [ 21.340910] Bluetooth: hci0: BCM: 'brcm/BCM.hcd' [ 21.344270] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 21.382993] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
With kernel 6.12.8 makes my Raspberry Pi 4 completly unresponsive if I try to do a reboot with: sudo shutdown now -r
The system boots then hangs indefinitely, forcing a power unplug to be able to boot again.
I found the same problem as 6.12.7 with resume on suspend, with AMD Radeon Vega 7 gpu. Downgrading to 6.12.4 restores normal functionality.