It works for me

works in a VM.

Works for me. The enabled Default and Performance tests pass OK. Test logs manually uploaded.
Work Station, Asus prime mobo - Ryzen5 5600g/AMDGPU 400 Series Chipset, (UEFI) Secure boot, SSD's > RAID1 (ext4) running Plasma DE.

default & performance tests pass (KVM)

fpaste --sysinfo

https://paste.centos.org/view/c785bf6d

Working fine on a bare-metal machine running Fedora Silverblue. Secure Boot is enabled and all tests met expectations.

Working fine on Virt-manager
KVM/QEMU Standard PC (Q35 + ICH9, 2009) (pc-q35-7.2) firmware UEFI (virt-manager default, secboot on)

works fine on NUC11PHK but the NIC's LED goes dark when the igc driver is loaded... LED remains dark until reboot.

kernel 6.9.x comes with a new CONFIG_IGC_LEDS kernel option

 $ grep -i CONFIG_IGC_LEDS  /boot/config-6.9.4-200.fc40.x86_64 
 CONFIG_IGC_LEDS=y
 $ grep -i CONFIG_IGC_LEDS  /boot/config-6.8.*
 $

 https://cateee.net/lkddb/web-lkddb/IGC_LEDS.html
 depends on: ( CONFIG_IGC && CONFIG_LEDS_CLASS ) && ( CONFIG_LEDS_CLASS = CONFIG_y || CONFIG_IGC = CONFIG_m )

 $ sudo dmesg |grep igc
 [    3.874237] igc 0000:59:00.0: enabling device (0000 -> 0002)
 [    3.874442] igc 0000:59:00.0: PTM enabled, 4ns granularity
 [    3.925396] igc 0000:59:00.0 (unnamed net_device) (uninitialized): PHC added
 [    3.956260] igc 0000:59:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x1 link)
 [    3.956265] igc 0000:59:00.0 eth0: MAC: <DELETED>
 [    4.200685] igc 0000:59:00.0 enp89s0: renamed from eth0
 [    8.478120] igc 0000:59:00.0 enp89s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

 $ grep  -e CONFIG_IGC_LEDS -e CONFIG_IGC -e CONFIG_LEDS_CLASS=   /boot/config-6.9.4-200.fc40.x86_64 
 CONFIG_IGC=m
 CONFIG_IGC_LEDS=y
 CONFIG_LEDS_CLASS=y

Default test pass, but "performance" #2271375 won't run; works great otherwise.

Working fine on baremetal too

Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz         
Graphics Processor: Mesa DRI Intel® HD Graphics 4000. driver: i915 v: kernel arch: Gen-7          
wi-fi: Qualcomm Atheros AR9485 Wireless Network. Adapter vendor: Lite-On. driver: ath9k v: kernel.

kernel tests PASSED

Works and passed test cases

Sysinfo: https://paste.centos.org/view/f7b0155d

Works.

There is something wrong with the systemd-modules-load.service, it seems that v4l2loopback module has a invalid signature. here is the log:

× systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: failed (Result: exit-code) since Thu 2024-06-13 19:28:54 CST; 1min 45s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 1716 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 1716 (code=exited, status=1/FAILURE) CPU: 21ms

6月 13 19:28:54 asus-zenbook-14-ux3405ma systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules... 6月 13 19:28:54 asus-zenbook-14-ux3405ma systemd-modules-load[1716]: Module 'msr' is built in 6月 13 19:28:54 asus-zenbook-14-ux3405ma systemd-modules-load[1716]: Failed to insert module 'v4l2loopback': Key was rejected by service 6月 13 19:28:54 asus-zenbook-14-ux3405ma systemd-modules-load[1716]: Failed to insert module 'v4l2loopback': Key was rejected by service 6月 13 19:28:54 asus-zenbook-14-ux3405ma systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE 6月 13 19:28:54 asus-zenbook-14-ux3405ma systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. 6月 13 19:28:54 asus-zenbook-14-ux3405ma systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules.

Everything works.

However would like to highlight this regression "After "Resume thermal zones asynchronously" commit: Wrong Battery Reading after Wake from S3 Sleep - Lenovo Thinkpad P1 Gen2" still not fixed.

Last known working kernel 6.7.x Bug present in whole of 6.8.x releases.

Upstream bug report source: https://lore.kernel.org/lkml/829c478d-f547-4e12-9976-ed465dd8d4ed@yahoo.de/T/ https://bugzilla.kernel.org/show_bug.cgi?id=218881

Resolves #2284279

works fine, not sure if related but chrome crashed x3 times when started it. I opened chrome, and it showed alerts that an extension crashed for each extension (all the installed extensions seemed to crash)

Fine in my laptop

https://paste.centos.org/view/0f5f5e80

I tested on a Silverblue VM (using virt-manager) and it worked just fine.

LGTM; no regressions on a Framework 13 AMD 7840U; Secure boot enabled, LUKS+btrfs, GNOME on Wayland.

Seems to work well just like all previous 6.9.{0..3}

6.9.4-200.fc40.x86_64 works fine on AMD Ryzen 7 PRO 6850U. cat /proc/sys/kernel/tainted = 0. I work with it for several hours now in an SELinux-confined user account (sysadm_u). Fedora KDE Spin. Up to date as of now with stable repos, plus the new kernel from here. Everything as expected.

Working fine here.

Works fine on Intel Core i5-3570K+AMD Radeon RX6700.

No problems here. OK. Ryzen 3700x, Rog Strix B550-F, nvidia from rpmfusion.

Works on an upsquared x86 Atom device, a HP AMD microserver (RAID-1 MD), various aarch64 systems inc MacBin, Jetson (Orin AGX, Xaiver AGX, Xavier NX, nano), RPi (RPi3, RPi4, Zero2W), Rock960, Rock5B, Pine64+, Lenovo X13s.

Works for me.

Works without issues till now

I experience that when I go to battery mode (so just plug off from power), my screen turns very bright, I think contrast level or some other screen value is strongly adjusted. Once I plug power in again, everything is fine again. My day/night and energy-saving (battery & plugged-in) options remain unchanged. It definitely is not the day/night, because this one can be enabled and disabled, but both modes are affected when plugged off.

Also, my notebook is no longer able to remain in standby (S2) if I close the lid: Once I close the lid, it takes about a second until it wakes up in this condition.

I am not yet 100% sure if it is the kernel since I was not using these functions since a few other updates as well, but it might be mentioned since I think there was no other update that could cause such a change. I try to find some time soon to identify if it is related to the kernel and check the logs. So I leave karma positive for now. Ain't critical anyway.

Beyond that, the kernel remains working fine.

Seems to work fine on bare-metal HP Z440, AMD RX570 with UEFI. Kernel regression tests both PASS, as did the previously released 6.9.{1...3} kernels from koji.

Works for me

Upgraded without issue. NFS problems appear to be resolved.

With regards to the battery/screen issue:
https://bugzilla.redhat.com/show_bug.cgi?id=2292514 (occurs always with 6.9.4-200 and never with other kernels)

With regards to the standby/lid issue:
https://bugzilla.redhat.com/show_bug.cgi?id=2292520 (not sure yet, but I expect this the kernel is not the origin of this)

Fine of Lenovo P16s AMD Gen2. Modern standby, boot, sound... everything works fine. Kernel tests run and uploaded.