The 6.0.5 stable kernel rebase contains new features, improved 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-2022-c4057cabb4Please login to add feedback.
| 0 | 8 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
"./runtests.sh" and "./runtests.sh -t performance" both PASS on Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3).
Have been running earlier versions of 6.0.x in normal use for 10 days and 6.0.5 for 18 hours without any problems.
This update's test gating status has been changed to 'failed'.
Works well on P1 Gen 2
This update's test gating status has been changed to 'passed'.
Works for me.. I have been running 6.0.x since the test week, no issues on this Box. The enabled Default and Performance tests pass OK.
AMD 965, x86_64 Work Station (legacy BIOS) SSD's > RAID1. Plasma DE from Zawertun's COPR. nVidia GT1030 card using nVidia RPM's from RPMFusion (520.56.06)
Default & performance tests pass (KVM)
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:9m42.291s user:4m20.567s sys:4m35.736s
sedna: laptop 8GB Intel i5-2520M CPU Lenovo T420 (SSD only) real:9m2.353s user:3m24.586s sys:4m31.661s
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) rea1:14m39.714s user:6m27.723s sys:5m58.087s
*** 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!
Default & performance tests pass (KVM)
Working fine both native and in a VirtualBox VM. Interestingly in VirtualBox guests, the timer-overhead test is consistently working in Fedora 35, 36 and 37 and that's virtually unheard of.
works for me on Dell Inspiron 3180 11"
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
I see message after 6.0.5 update
[ 3.656713] systemd[1]: bpf-lsm: Failed to load BPF object: No such process
With 5.19.16
systemd[1]: bpf-lsm: LSM BPF program attached
Working fine on KVM/Qemu/VirtManager
./runtests.shPASS on 6.0.5-300.fc37.x86_64 on virtual machine in KVM/QEMU (Host Intel Core i7-4720HQ, NVIDIA GM204M [GeForce GTX 970M] driver: nouveau). VM installed using Fedora-KDE-Live-x86_64-37-20221014.n.0.iso (updated as of now with updates-testing). No modifications beyond dnf update.Immediately before I executed runtests.sh: cat /proc/sys/kernel/tainted -> 0
Immediately after I executed runtests.sh: cat /proc/sys/kernel/tainted -> 8192
It boots properly & I experience no issues so far.
./runtests.sh -t performancenot tested."Failed to load BPF object" is kernel issue or systemd?
Works.
not seeing the other issues noted, working fine for me
I'm seeing "Failed to load BPF object" here too. The error comes from libbpf, when it tries to load the kernel BTF. I'll file a bug against libbpf to track this.
That has been around a while. Maybe related to:
https://bugzilla.redhat.com/show_bug.cgi?id=2084955
https://bugzilla.redhat.com/show_bug.cgi?id=2138510
No. #2084955 was about a different return code and an error in a different place. Anyway, let's continue the discussion in the #2138510.
This version works as intended and also fixes this bug related to resume on Dell Inspiron 2-in-1: https://bugzilla.redhat.com/show_bug.cgi?id=2123576 It also passes the test case kernel regression.
Works fine on a bunch of arm devices
adamwill edited this update.
This update has been submitted for stable by jforbes.
jforbes edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jforbes.
jforbes edited this update.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
Commented above on previous kernel (6.0.5). Repeated the tests for 6.0.5
kernel 6.0.6-300.fc37: Ran default and performance regression tests and both PASS on Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3).
Tested on KDE spin, on VM with nomodeset and basic video driver, and bug seems to be fixed, plasma-wayland session started fine.
Same setup with previous kernel version hanged just like described on the bug ticket.
This update has been submitted for stable by bodhi.
6.0.6-300.fc37.x86_64 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:10m35.975s user:4m35.870s sys:4m57.594s
sedna: laptop 8GB Intel i5-2520M CPU Lenovo T420 (SSD only) real:18m29.320s user:10m3.345s sys:7m15.312s
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) rea1:19m54.491s user:9m38.595s sys:7m37.750s
*** 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!
Default & performance tests pass (KVM)
Default & performance tests PASS
@jforbes : we're missing kernel-headers & kernel-tools 6.0.6?
Works for me.. The enabled Default and Performance tests pass OK.
Also fixes #2138510
AMD 965, x86_64 Work Station (legacy BIOS) SSD's > RAID1. Plasma DE from Zawertun's COPR. nVidia GT1030 card using nVidia RPM's from RPMFusion (520.56.06)
@carlg There is only one Headers and Tools build every minor release, e.g. 5.19. 6.0.
my placeholders got messed up in my example, I meant 5.19.y and 6.0.y etc.
Default & performance tests pass (KVM)
Isn't this supposed to get pushed to stable, given it addresses a blocker?
Regression tests successful. Working as expected on my X1 Carbon.
This update has been pushed to stable.