[Bug 222146] New: 6.18: AMD (Ryzen 5): cannot select existing energy_performance_preference

[bugzilla-daemon@kernel.org]

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

            Bug ID: 222146
           Summary: 6.18: AMD (Ryzen 5): cannot select existing
                    energy_performance_preference
           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: steffen@sdaoden.eu
        Regression: No

Hello!  I sail 6.18.newest and since some weeks (possibly: since "custom",
whatever this is, is listed) my self-knitted "cpupower" shell script fails like
so:

  /root/bin/cpupower.sh: 1: echo: echo: I/O error
  ERR:CPU 0: write for energy_performance_preference=balance_performance failed

Ie it cannot set that even though it is reported to exist (the script refetches
what is available after settings are changed):

  CPU 0: freq: 406477-3201000; scaling: 406477-3201000; boost:0; gov: powersave
(performance powersave); energy: performance (default performance
balance_performance balance_power power custom)

On the terminal:

  #?0|lecce:~# cat
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences
  default performance balance_performance balance_power power custom
  #?0|lecce:~# echo balance_performance >
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference
  -su: echo: write error: Device or resource busy
  #?1|lecce:~# cat
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference
  performance

It works when i switch to all-performance, when i build, for example:

  CPU 0: freq: 406477-4979334; scaling: 406477-4979334; boost:1; gov:
performance (performance powersave); energy: performance (performance)

And it worked everwhere just smoothly before.

Thanks again, a lot.  I love it!

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

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