TLDR version: There is a regression in power handling on kernel 6.15.11 and 6.16.3, due to bug(s) in AMD suspend/resume code within the kernel. Patch against kernel 6.17-rc3 to potentially fix the bug is available from Mario Limonciello (AMD): https://lore.kernel.org/linux-pm/20250826052747.2240670-1-superm1@kernel.org/T/#uncategorized Could you apply the patch to Fedora kernels? Other relevant bug reports: * https://bugzilla.kernel.org/show_bug.cgi?id=219981 * https://community.frame.work/t/increased-power-usage-after-resuming-from-suspend-on-ryzen-7040-kernel-6-15-regression/74531 * https://github.com/redhat-performance/tuned/issues/789 Problem description - long version: After coming out of suspend, the actual energy preference is always reported as "performance", even though it was set to "power" before suspend. The regression does NOT occur on kernel 6.14.11 (everything else is the same except kernel version). Machine setup: Framework AMD FW13 laptop, AMD Ryzen 5 7640U. Using Fedora 41, tuned-2.25.1-2, kernel 6.15.11 / 6.16.3, gnome-shell 47.9, latest framework bios (3.16). How to reproduce: Before suspend: using the gnome shell top-right menu to set the power mode to "Power Saver", which under the hood uses TuneD. The change in the energy preference after the resume is NOT reflected in the gnome shell top-right menu (still says "Power Saver"). However, the actual mode can be seen via the cpupower command (part of kernel-tools). State before suspend according to cpupower: $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate-epp CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 energy performance preference: power State after resuming from suspend according to cpupower: $ sudo cpupower frequency-info analyzing CPU 6: driver: amd-pstate-epp CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 energy performance preference: performance 2. What is the Version-Release number of the kernel: Known affected kernels: kernel-6.15.11-100.fc41.x86_64 kernel-6.16.3-100.fc41.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Known to work properly with: kernel-6.14.11-200.fc41.x86_64 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes, see the "Long version" section above. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Haven't tried, though I did try kernel-6.16.3-100.fc41.x86_64 from koji: https://kojipkgs.fedoraproject.org/packages/kernel/6.16.3/ 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Reproducible: Always
Created attachment 2104979 [details] dmesg.txt associated dmesg.txt (generated via "sudo journalctl --no-hostname -k > dmesg.txt") on kernel 6.16.3
Additional info. Same problem with kernel-6.15.3-100.fc41.x86_64, as obtained from koji. Last known good kernel: kernel-6.14.11-200.fc41.x86_64 First known bad kernel: kernel-6.15.3-100.fc41.x86_64
@jforbes could you build a Fedora test kernel with that patch? It would be good to confirm it's the same issue and Golden Spinach doesn't have the ability to build kernels.
https://koji.fedoraproject.org/koji/taskinfo?taskID=136475609
I tested the kernel and can confirm that the amd-pstate patch has fixed the regression. The "energy performance preference" (as reported by cpupower) now stays the same after a suspend + resume. Thanks to jforbes for building the kernel with the patch, and to Mario Limonciello for creating the patch.
FEDORA-2025-94b0d1f2b6 (kernel-6.16.5-200.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-94b0d1f2b6
FEDORA-2025-683130d488 (kernel-6.16.5-100.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-683130d488
FEDORA-2025-683130d488 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-683130d488` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-683130d488 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-94b0d1f2b6 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-94b0d1f2b6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-94b0d1f2b6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-94b0d1f2b6 (kernel-6.16.5-200.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-683130d488 (kernel-6.16.5-100.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
Here's the mainline commit ID with the fix just to wrap this up. https://github.com/torvalds/linux/commit/ba3319e5905710abe495b11a1aaf03ebb51d62e2