-
-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CPU not scaling up in battery mode [Kernel 5.17 with amd-pstate driver] #398
Comments
After i upgraded the Kernel from 5.13 to 5.18 and initialized AMD_PSTATE it started working properly. /etc/autocpufreq.conf file and AMD's CPPC driver settings are given below. /etc/auto-cpufreq.conf file example
And AMD settings from here
|
Hey, thanks for your answer! Unfortunately the config file did not change the behaviour when on battery and under full load. CPU is still not scaling over the scaling_min_freq (now ~1.1GHz). To clarify my problem a bit more, here is the output of "auto-cpufreq --debug" under full CPU load on battery, as well as plugged-in. On battery (with above config-file)Using settings defined in /etc/auto-cpufreq.conf fileLinux distro: Manjaro Linux 21.2.6 Qonos ------------------------------ Current CPU stats ------------------------------ CPU max frequency: 4372 MHz Core Usage Temperature Frequency auto-cpufreq version: 1.9.4 Python: 3.10.4 Computer type: Convertible auto-cpufreq system resource consumption: Total CPU usage: 100.0 % Currently using: powersave governor Plugged in (with above config-file)Using settings defined in /etc/auto-cpufreq.conf fileLinux distro: Manjaro Linux 21.2.6 Qonos ------------------------------ Current CPU stats ------------------------------ CPU max frequency: 1801 MHz Core Usage Temperature Frequency auto-cpufreq version: 1.9.4 Python: 3.10.4 Computer type: Convertible auto-cpufreq system resource consumption: Total CPU usage: 100.0 % Currently using: performance governor |
Having simiar issue when using amd-pstate on battery mode. Even when turbo boost kicks in it never gets over min cpu freq Stats:
|
Looks like this is amd-pstate behavior with "powersave" governor and it should be replaced with "ondemand" instead |
@riskingh I do not own AMD CPU hence I cannot test this. If you or anyone else wants to submit a PR which could potentially resolve this problem that would be great, as I always encourage users to submit code contributions and credit everyone for their work. |
@AdnanHodzic I'm not a big fan of changing existing behavior, which is why my solution to this was to submit the (now merged) PR to add config files. It seems a lot of people would be expecting the behavior of the |
@zoitrok I think you're absolutely right. According to arch-wiki, the powersave-governor always sets the frequency at it's minimum. I wasn't aware of that before. Nevertheless, I think there is something fishy about the amd-pstate driver. I experience sometimes weird behaviour when using it. Can anyone confirm that, or might it just be my individual setup? For now I went back to acpi-cpufreq driver and upgraded to kernel 5.18. Using an adjusted config file, I now get the desired results. Under full load, the Ryzen 7 5700U scales up to 2.3 GHz in charging-mode as well as in battery-mode. Even though it's capable of up to 4.3 GHz, I think it might be limited due to thermals (~75°C @2.3GHz, full load) - am I right? Below is my current config file for those who are interested. Min and max frequencies are adapted to my specific CPU.
|
@mldytech turbo=auto leaves it up to auto-cpufreq to enable the turbo. It takes a bit of sustained load to kick in. In my world keeping it on 'always' gives a more responsive system with no real hit to heat or battery. |
Hello, I can reproduce. Yesterday night I got |
Closing the issue due to inactivity. If there are any changes that could be made please give it a try and contribute to the project and you will be credited for your work as part of future release. |
I have the same CPU. I was able to correct being locked at 500Mhz by changing to governor = conservative under battery in auto-cpufreq.conf |
Thanks a lot! |
This issue seems to be resolved, closing. |
Hello,
first of all thanks for this very helpful tool.
I just installed kernel 5.17 (including the new amd-pstate driver) on my system and am experiencing weird behaviour when using auto-cpufreq. First of all, the "min" and "max" frequencies seem to adjust dynamically (seen in auto-cpufreq --stats).
I tested the following scenarios while running prime95 (full cpu-load simulation). When charging, the freq goes only up to 2.3 GHz on all cores, and in battery mode I barely reach 1 GHz. I also experienced low frequencies (when on battery) with kernel 5.15 and the acpi driver.
I tried installing auto-cpufreq through the AUR package, as well as from source.
Am I doing something wrong, or is using the new amd-pstate driver a bad idea in general?
Thank you very much!
Output of auto-cpufreq --debug
### System information:Base clock = 1.8 GHz
Boost = up to 4.3 GHz
Linux distro: Manjaro Linux 21.2.6 Qonos
Linux kernel: 5.17.9-1-MANJARO
Processor: AMD Ryzen 7 5700U with Radeon Graphics
Cores: 16
Architecture: x86_64
Driver: amd-pstate
------------------------------ Current CPU stats ------------------------------
CPU max frequency: 1801 MHz
CPU min frequency: 400 MHz
Core Usage Temperature Frequency
CPU0: 5.8% 51 °C 1801 MHz
CPU1: 1.0% 51 °C 1776 MHz
CPU2: 5.0% 51 °C 1801 MHz
CPU3: 0.0% 51 °C 1801 MHz
CPU4: 1.0% 51 °C 1801 MHz
CPU5: 1.0% 51 °C 1801 MHz
CPU6: 1.0% 51 °C 1801 MHz
CPU7: 0.0% 51 °C 1801 MHz
CPU8: 2.0% 51 °C 1801 MHz
CPU9: 0.0% 51 °C 1801 MHz
CPU10: 0.0% 51 °C 1801 MHz
CPU11: 0.0% 51 °C 1801 MHz
CPU12: 1.0% 51 °C 1801 MHz
CPU13: 0.0% 51 °C 1801 MHz
CPU14: 7.4% 51 °C 1801 MHz
CPU15: 0.0% 51 °C 1801 MHz
auto-cpufreq version: 1.9.4
Python: 3.10.4
psutil package: 5.9.1
platform package: 1.0.8
click package: 8.1.3
distro package: 1.7.0
Computer type: Convertible
Battery is: charging
auto-cpufreq system resource consumption:
cpu usage: 0.0 %
memory use: 0.07 %
Total CPU usage: 2.3 %
Total system load: 0.38
Average temp. of all cores: 50.88 °C
Currently using: performance governor
Currently turbo boost is: off
The text was updated successfully, but these errors were encountered: