[Bug 220013] New: [REGRESSION, BISECTED] acpi-cpufreq: Boost disablement not being restored after resume from suspend

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220013

            Bug ID: 220013
           Summary: [REGRESSION, BISECTED] acpi-cpufreq: Boost disablement
                    not being restored after resume from suspend
           Product: Power Management
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: nic.c3.14@gmail.com
        Regression: No

On kernel 6.13.8, disabling boost by setting
/sys/devices/system/cpu/cpufreq/boost to 0 would persist after resuming from
suspend. After updating to 6.14.2, the system is able to enter boost states
after resuming from suspend despite the boost flag still being set to 0.
Toggling it to 1 and then back to 0 in this state re-disables boost. My system
uses the acpi-cpufreq driver.

Hardware: AMD Ryzen 7 2700U

Steps to Reproduce:
1. Disable boost by writing 0 to /sys/devices/system/cpu/cpufreq/boost
2. Place the system into S3 suspend
3. Wake the system. /sys/devices/system/cpu/cpufreq/boost` should still be 0.
4. Place a load on the processor to cause the system to enter a boost state,
such as running `stress -c 4`.
5. The processor boosts

I have bisected this to commit 2b16c631832df6cf8782fb1fdc7df8a4f03f4f16
("cpufreq: ACPI: Remove set_boost in acpi_cpufreq_cpu_init()").

This issue persists with mainline master (commit 004a365eb8b9 ("Merge tag
'erofs-for-6.15-rc2-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs") at the time of
testing). Reverting commit 2b16c631832d restores the previous behavior (not a
clean revert; needed to merge with be6b8681a0e4c1477a2c1cb155f7b9188aa88acb
("cpufreq: acpi: Set policy->boost_supported"))

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.