The 6.2.6 kernel rebase contains new feature, additional hardware support, and 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-6c21cbb2cf
Please login to add feedback.
0 | 12 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
Default & performance tests pass (KVM)
Works for me.. I have been running the 6.2.x kernels since the test week started with no issues noticed. The enabled Default and Performance tests had all passed OK.
Work Station running Ryzen5 5600g/AMDGPU 400 Series Chipset. (UEFI + secure boot). SSD's > RAID1 (ext4) , running Plasma DE from Zawertun's COPR.
This update's test gating status has been changed to 'passed'.
With Kernel 6.2.x my 01:00.0 Wireless controller [0d40]: Intel Corporation XMM7560 LTE Advanced Pro Modem (rev 01) stops working with following errors: e.g. [ 33.004399] iosm 0000:01:00.0: ch[1]: confused phase 2
I filed a bug report last week https://bugzilla.redhat.com/show_bug.cgi?id=2175487 but noone responded sadly
I also tired to contact linuxwwan@intel.com but have also not heared anything from them. Maybe this downvote triggers an investigation?
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
Works for me: all using the Mate Desktop Environment.
sirius: desktop 16GB Intel i7-3770 CPU desktop (SSD + 5 hard drives in RAID-6) real:10m59.698s user:4m36.802s sys:5m15.305s
sedna: laptop 8GB Intel i5-2520M CPU Lenovo T420 (SSD only) real:108m12.436s user:71m35.438s sys:34m51.867s
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) rea1:15m37.432s user:6m59.002s sys:6m5.237s
*** I’m intensely curious as to the reason for why sedna seems to randomly fluctuate between short (normally under 11 minutes) & extremely long (100+ minutes) elapsed times for the performance test!
i7-9700K(UHD Graphics 630): kernel regression test passed. Works fine for daily use.
Works great. Ryzen 3700x, nvidia graphics from rpmfusion, Rog Strix B550-F. Regression and performance tests passed. Even shaved a few seconds off of boot time.
Default and performance pass. HP Prodesk 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD Graphics 630]
Works for me.
CPU: Intel 12900K Motherboard: Asus ROG Strix z690-G Gaming WiFi NVME SSD: Samsung 980 Pro 500Gb RAM DDR5: 2 x 16 Gb DDR5 4800 Video Card: MSI Nvidia RTX 3080 Ti
Works on Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000. wi-fi: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel
Cachedrop test failed at first run but passed other three times, so kernel regression tests sucessfull.
Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (525.89.02) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
Not sure if it's kernel related or not, but one of my machines started spitting this message out on boot with the 6.2.x kernels, but seems to be working fine otherwise. The other machines I've got 6.2.6 running on are working without problems. kernel regression tests pass.
Seems to be working OK in a VirtualBox VM. Regression tests passing.
Works great on Lenovo T480! LGTM! =)
Everything seems to be running smoothly. CPU: AMD Ryzen 7 5700X GPU: AMD ATI Radeon RX 6750 XT RAM: Corsair Vengeance Pro 64GB (4X16GB) DDR4 3600 HDD: SAMSUNG 980 PRO SSD 2TB PCIe NVMe Motherboard: ASUS AM4 TUF Gaming X570-Plus
Works fine, no regressions noticed. Intel Skylake-X, Nvidia Turing (proprietary drivers)
Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3). Default and Performance tests passed.
Dell XPS 13 9350, Intel Core i7-6560U × 4, Mesa Intel Iris Graphics 540 (SKL GT3). Default and Performance tests passed.
SilverBlue on F37 on another Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3). Default and Performance tests passed.
Also running it on my main PC, all without any problems on any of the 4 machines.
The instructions you get to from the Fedora Magazine article didn't work for me. It didn't work with the wildcard '' when installing. I had to use the full filename. Then it installed and worked fine. This is what didn't work for me: 'rpm-ostree override replace kernel-.rpm --install=kernel-modules-core-*.rpm'. That's on https://fedoraproject.org/wiki/Test_Day:2023-03-05_Kernel_6.2_Test_Week
Tried to update the kernel on a silverblue system using the instructions for the test week and it failed to update. I've updated the kernel and tested on a
Editing problem in the last 2 paragraphs of my comment immediately above. That was about the instructions for installing the kernel update on SilverBlue, I don't see why the instructions wouldn't work - so my guess is there was something else going on and the instructions are fine.
Default & perf tests passed on esxi 6.7
jforbes edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jforbes.
Thanks for updating to latest; do we need to update headers? If not it would probably make sense to push to stable and submit new version and keep version aligned. Unless there was an issue with 6.2.6?
Works for me: all using the Mate Desktop Environment.
sirius: desktop 16GB Intel i7-3770 CPU desktop (SSD + 5 hard drives in RAID-6) real:10m55.133s user:4m34.336s sys:5m15.120s
sedna: laptop 8GB Intel i5-2520M CPU Lenovo T420 (SSD only) real:107m47.409s user:71m15.231s sys:34m45.735s //// Took more than 10 times longer than normal!
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) rea1:15m33.506s user:7m0.503s sys:6m3.358s
*** I’m intensely curious as to the reason for why sedna seems to randomly fluctuate between short (normally under 11 minutes) & extremely long (100+ minutes) elapsed times for the performance test!
(applies to 6.2.7) looks good to me, regression tests passing.
kernel-6.2.7-200.fc37 Default and performance pass. HP Prodesk 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD Graphics 630]
Default & performance tests pass (KVM)
Works for me.. The enabled Default and Performance tests pass OK.
Work Station running Ryzen5 5600g/AMDGPU 400 Series Chipset. (UEFI + secure boot). SSD's > RAID1 (ext4) , running Plasma DE from Zawertun's COPR.
FWIW the change enabling
-funsigned-char
on 6.2 by default (3bc753c06dd0 ("kbuild: treat char as always unsigned")) already broke at least 2 kernel drivers, with possibly more expected to come:https://lore.kernel.org/linux-input/e20db4c4-b2a8-bc88-232f-d1213733d20c@leemhuis.info/ https://lore.kernel.org/linux-input/d2d0baef-c15b-3abf-338c-77de403c262c@qtmlabs.xyz/
Considering the wide ranging implications of that kernel change, especially to kernel drivers that was only ever used on x86/x86_64 platforms (where
char
is signed by default), I would suggest staying on 6.1 a bit longer until we are sure that the drivers are fixed.Negative karma per above.
./runtests.sh
PASS with koji's kernel-6.2.7-200.fc37.x86_64 and kernel-headers-6.2.6-200.fc37 builds (without kernel-tools-6.2.6-200.fc37) within a kvm/qemu VM (KDE spin, up to date with all testing repos enabled) on a AMD Ryzen 6000 mobile series host. No third party modules (tainted = 0).I tested the VM some minutes with average activities, works fine so far. No errors/issues when using it.
With 6.2.7 am getting this in dmesg: systemd[1]: bpf-lsm: Failed to load BPF object: No such process. Ryzen 3700x, nvidia from rpmfusion, Rog Strix B550-F. Aside from this no problems. Regression tests passed as well as performance tests. However I do have way more than usual "failed" in perf test which started with 6.2.6. Generally functional.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (525.89.02) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
Dell XPS 13 9350, Intel Core i7-6560U × 4, Mesa Intel Iris Graphics 540 (SKL GT3). Default and Performance tests passed.
kernel 6.2.7 seems fine on my laptop.
Works well on Lenovo THinkPad P1 Gen2
I am not an expert! This kernel version does not work with my Realtek WiFi using the provided rtw89_8852be module. I found a similar bug report at SUSE: https://bugzilla.opensuse.org/show_bug.cgi?id=1209449 "Realtek knows"
@tilltyr as mentioned in the bug you linked, this is not a kernel issue. It was a linux-firmware issue, and the fix will also happen there. The reason firmware issues can appear to be tied to a kernel version is because those firmware get copied into the initramfs, and do not change when you change the version of linux-firmware installed on the system unless you also regenerate an initramfs. You should be able to revert your firmware packages to an earlier version of linux-firmware, and recreate your initramfs to end up with a working 6.2.7 kernel.
No issues so far on 12700K, 3080 with proprietary drivers, 2.5G LAN and stuff. No WiFi to cause issues though.
@jforbes, thanks for the clarification! Unfortunately, it seems I cannot change my -1 Karma above, therfore I gave a +1 here to even it out!
kernel-6.2.7-200.fc37 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.
Do we any major regressions preventing this going to stable?
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
I have been using this kernel for about a week and have had many issues with the AMDGPU driver on my Alienware M17r5. It has an AMD Radeon 680m iGPU, and a Radeon 6850m XT dGPU. I can't get it to happen all the time. Still, in most cases, if I use a multi-monitor setup via a USB-C dock, right-click and run an application using the dGPU and move it from one desktop to the other, or if I have VBOX open for too long, it errors out. When it starts erroring, the desktop is still "useable," but the performance is significantly hindered, and there are artifacts. It doesn't happen with the 6.3 kernels and any of the latest 6.1* stable kernels. This would happen previously with IOMMU enabled, so I tried specifically enabling with a kernel boot param, and again disabled, still the same results:
I can give more details if required, but I am attaching some here:
[ 3370.709726] amdgpu 0000:37:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 3370.709735] amdgpu 0000:37:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 3370.709744] amdgpu 0000:37:00.0: amdgpu: RW: 0x0 [ 3370.709759] amdgpu 0000:37:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32771, for process gnome-shell pid 3159 thread gnome-shel:cs0 pid 3187) [ 3370.709776] amdgpu 0000:37:00.0: amdgpu: in page starting at address 0x0000800101811000 from client 0x1b (UTCL2) [ 3370.709788] amdgpu 0000:37:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031 [ 3370.709797] amdgpu 0000:37:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [ 3370.709808] amdgpu 0000:37:00.0: amdgpu: MORE_FAULTS: 0x1 [ 3370.709816] amdgpu 0000:37:00.0: amdgpu: WALKER_ERROR: 0x0 [ 3370.709825] amdgpu 0000:37:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 3370.709834] amdgpu 0000:37:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 3370.709843] amdgpu 0000:37:00.0: amdgpu: RW: 0x0 [ 3370.709859] amdgpu 0000:37:00.0: amdgpu: IH ring buffer overflow (0x0008A560, 0x00009C00, 0x0000A580) [ 3370.717833] [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx_0.0.0 timeout, but soft recovered