@seb128 Thanks for looking into it. I update the description, please check if it is more explicit to you.
The Thermal management policy requires to align with the node /sys/firmware/acpi/platform_profile, which is created by the platform_profile driver. 6.8 kernel didn't have the driver, therefore, it won't take effect on those platforms with 6.8 kernel. For Noble user who is on 6.8 kernel, when they switch power mode, the system CPU still scaling the frequency, but it can have the optimized thermal management rule for the platform. -- You received this bug notification because you are a member of Debcrafters packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2115041 Title: Can't recognize custom ACPI platform profile Status in OEM Priority Project: New Status in power-profiles-daemon package in Ubuntu: In Progress Bug description: [ Impact ] * The AMD and Intel pstate driver will change CPU frequency control mechanism against different power mode setting in the PPD. To support the mechanism fully it needs to adapt correct thermal management policy in the BIOS which is determined by the USTT(User Selectable Thermal Table), and it is reflected by the platform profile. The feature will change the ThermalManagement setting after reboot when user change the power mode setting. The mapping relationship power mode and platform profiles: performance <-> performance balanced <-> balanced/balanced_performance/cool power saver <-> low-power/quiet [ Test Plan ] * On AMD Strix Point/Krackan Point platform which has sysfs node /sys/firmware/acpi/platform_profile * Try to modify power mode by $ sudo powerprofilectl set <power-mode> * Check if /sys/firmware/acpi/platform_profile being updated * After reboot, check if BIOS update the ThermalManagement setting by $ fwupdmgr get-bios-setting ThermalManagement [ Where problems could occur ] * The platform will list supported platform_profile in /sys/firmware/acpi/platform_profile_choices, the DPP power mode should map to one of it, otherwise, it can't select the correct thermal policy. If the platform set the unexpected string which the mapping is not defined in the PPD. The thermal policy can't be switched successfully. [ Other Info ] * Upstream commit: https://gitlab.freedesktop.org/upower/power- profiles-daemon/-/commit/6b565b0b05a2bc92e3c546a567b394f415937265 * The patch is in 25.04 and 25.10 already. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2115041/+subscriptions -- Mailing list: https://launchpad.net/~debcrafters-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~debcrafters-packages More help : https://help.launchpad.net/ListHelp
