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.

6.6.10-200.fc39.x86_64 works fine on an AMD Ryzen 7 PRO 6850U host: F39 KDE Spin (up to date with stable repos as of now, plus the 6.6.10-200.fc39 kernel from koji) with SELinux confined user account, uname -r = 6.6.10-200.fc39.x86_64, tainted = 0. So far it works fine with average activities.

Maybe I have later some time to run a regression test in the VM.

default & performance tests pass (KVM)

Working fine here, native and VM.

Intel NUC NUC13ANHi7 (NUC13ANHi7000) (rev N11225-207) 1 x 13th Gen Intel(R) Core(TM) i7-1360P Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)

Dell Precision T3600 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz (8 cores total) NVIDIA Corporation GF119 [NVS 310] (rev a1)

Intel NUC i7 NUC11PAH 1 x 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)

Works.

Thinkpad T14s, AMD Ryzen 7840U, Fedora 39, UEFI, Secure Boot, luks+btrfs. Default and performance tests pass OK. Suspend seems to work.

Working fine.

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.

Default fedora btrfs filesystem.
Suspension working.
Passed kernel regression tests.

No problems seen while running this kernel.

Works well

works fine

Works fine on my system. Ryzen 3700x, Rog Strix B550-F, Nvidia 2070 from rpmfusion. Secure boot disabled. UEFI.

Additional to my native test above: regression test ./runtests.sh PASS with kernel-6.6.10-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 (only the known issues of SELinux confined user accounts in KDE occur), uname -r = 6.6.10-200.fc39.x86_64, tainted = 0. Works fine with average activities: firefox browsing, dolphin file organization.

@acaringi the regression test passes, but I am worrying about the following line of the vulnerability status:

/sys/devices/system/cpu/vulnerabilities/spec_rstack_overflow:Vulnerable: Safe RET, no microcode

I am not sure if that is currently intended / known?

The full vulnerability status is the following:

/sys/devices/system/cpu/vulnerabilities/gather_data_sampling:Not affected
/sys/devices/system/cpu/vulnerabilities/itlb_multihit:Not affected
/sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
/sys/devices/system/cpu/vulnerabilities/mds:Not affected
/sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
/sys/devices/system/cpu/vulnerabilities/mmio_stale_data:Not affected
/sys/devices/system/cpu/vulnerabilities/retbleed:Not affected
/sys/devices/system/cpu/vulnerabilities/spec_rstack_overflow:Vulnerable: Safe RET, no microcode
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
/sys/devices/system/cpu/vulnerabilities/srbds:Not affected
/sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected

Kernel Docs indicate that the user space might be vulnerable in this condition:

The "Safe RET" mitigation (see below) has been applied to protect the kernel, but the IBPB-extending microcode has not been applied. User space tasks may still be vulnerable.

Looks hardly exploitable in practice as long as the system is configured with best-practices or defaults, but maybe some mitigation can be achieved in future?

No regressions here; CPU is AMD Ryzen 7 7840U w/ Radeon 780M Graphics

@py0x3 I booted 6.6.{7,8,9} and the same message appears in lscpu in all of them so if this a regression it doesn't look like it's this recent.

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.