The 6.6.7 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-2023-26ffe7d3c7
Please login to add feedback.
0 | 11 | Test Case kernel regression |
This update has been submitted for testing by acaringi.
This update's test gating status has been changed to 'waiting'.
Seems fine here, both native and as a VirtualBox VM.
This update's test gating status has been changed to 'passed'.
default & performance tests pass (KVM)
Why this have autokarma disabled, if the bug tracker for it says to do otherwise?
https://bugzilla.redhat.com/show_bug.cgi?id=2253633
Working fine
Default fedora btrfs filesystem. Suspension working Passed kernel regression tests
Default test passed (AMD 4500U using iGPU), no issues on my system. Thank you for the update!
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) running Plasma DE.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
Works well here. Ryzen 3700x, Rog Strix B550-F, Nvidia 2070 from rpmfusion, Intel SSD, secure boot disabled, amd_iommu=on iommu=pt, used for gaming.
GenMachine AMD Ryzen 7 4700U. Btrfs. Wayland.
Works fine.
Works for me.
Host: KVM/QEMU Standard PC (Q35 + ICH9, 2009) (pc-q35-7.2) CPU: Intel(R) Core(TM) i7-4790K (8) @ 3.99 GHz Memory: 1.50 GiB / 3.80 GiB (40%)
cachedrop regression FAIL
No performance tests done
I rerun and cachedrop PASSED and others regressions
@farribeiro for some reason it sometimes happens that cachedrop fails on the first run, but passes on any subsequent run, I don't know why. On VirtualBox guests, timer-overhead fails at least 50% of the time on any run.
ok
Thinkpad T14s, AMD Ryzen 7840U, Fedora 39, UEFI, Secure Boot, luks+btrfs. Default and performance tests pass OK. Suspend seems to work.
Regression test ./runtests.sh PASS with kernel-6.6.7-200.fc39.x86_64 within QEMU/KVM with CPU-passthrough on an AMD Ryzen 7 PRO 6850U host: F39 KDE Spin with SELinux confined user account (user_u), VM up to date as of now with updates-testing enabled, uname -r = 6.6.7-200.fc39.x86_64, tainted = 0. So far it works fine with average activities: firefox browsing, dolphin file organization.
Works fine on Lenovo ThinkPad P1 Gen 2
no issues with Thinkpad P1 gen 3
With this morning's Fedora 39 updates, Dec. 18, I am getting this in dmesg: Xorg[1553]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set. Have reinstalled Xorg and kernel 6.6.7 which, of course, did not fix the situation.
eems to work fine on bare-metal HP EliteBook 840 G6 with UEFI and SecureBoot. No issues to report so far and kernel regression tests both PASS.
Seems to work fine on bare-metal HP Z440, AMD RX570 with UEFI. Kernel regression tests both PASS, Bug 2252130 still present but OpenCL compute now working but with trace errors.
This update has been submitted for stable by acaringi.
This update has been pushed to stable.
Both kernel package - No display during boot, blank screen kernel-6.6.7-200.fc39.x86_64 kernel-6.6.6-200.fc39.x86_64
last working package: kernel-6.6.4-200.fc39.x86_64
P16 v2 -AMD Ryzen 7 PRO 7840U w/ Radeon 780M
Hm, noticed VBox modules are tained. Not sure if related to kernel or their end. Getting reports ever boot now.