-
-
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
Not respecting the config file #359
Comments
Try setting turbo boost to 'always', if turbo boost is off, your system limits the max frequently. |
can enabling that setting eat battery life? |
|
I see this confirmed here, I also saw another mentioned of this in another bug report, as this is a regression which I originally mentioned this to @bobslept as part of his #349 PR. In a nutshell, what was happening before and what was displayed as part of auto-cpufreq demo on Youtube is not happening for me anymore. Hence, if my CPU usage in % starts to increase and is above >= 70 or even in 100% range, instead of cores kicking in to their max, they'll never get there anymore. This is what my CPU stats look like while I'm stressing all of my cores:
I haven't had a time to look into this, but I'm sure one of the conditions as part of set_performance function is messing something up. In meantime, if anyone has time to look into this and make a code contribution that would be great! |
While building a kernel.
On battery with powersave governor it locks on 1400mhz. If change governor to |
@bobslept yea I remember that it worked for you when I initially mentioned this issue. Can you confirm you're also not using the auto-cpufreq config file? While I'm running on Intel ...
... it doesn't seem to be an Intel only thing as @Hikandy is running on Ryzen 7 and has this problem. Really hard to pinpoint what exactly is causing this behavior ... |
I'm not using the config file normally. He says speed is not going higher then 1600mhz. Which is exactly the same behavior I have using the So to get max speed when I need it on battery, I switch to Why I chose Btw @AdnanHodzic to pinpoint this, did you try set the stuff manually instead of letting Did you look into platform profiles that controls your power level? Added since 5.12. I mean if I set my profile to low-power it has a max of 20 watts to use if I'm correct. Then I never reach my 3.2ghz no matter how hard I try. That's why we made sure it was on balanced before stopping the
|
Neither am I, as I like auto-cpufreq to automatically figure what it needs to do. Regardless, I just configured auto-cpufreq config file to:
output during regular workload is better then it is when CPU is put under pressure ...
then I ran:
Then, I set for performance governor to be used on battery as well:
Ran stress test and during first iteration frequencies were unlocked and went really high (as they should in this scenario)
and next iteration they went lower
and they ended up settling on 1400Mhz, but were ranging between 1400 to 1700Mhz
I also performed stress test while laptop was discharging ... and same behavior in terms of frequencies while it was charging.
Finally, I changed both
I then even removed the auto-cpufreq config file, ran same stress test and results were again as they should be:
There we have it, using team work we managed to pinpoint the problem and that's what caps the frequencies on some hardware. Here's my suggestion how we could resolve this so it works as it should for everybody. 1: Leave power-profiles-daemon to be set to "balanced" before its disabled. Other option is to instruct people to change code and re-install auto-cpufreq (as I did) which is incredibly ugly and not really a solution. Would love to hear your thoughts.
Btw |
@AdnanHodzic I don't use power-profiles-daemon though so I don't think i can resolve it via your suggestions |
@AdnanHodzic If that profile does not fit the user they could set the system profile themselfs? If they have support for it. To get supported profiles from your system: Set it to performance profile for example: I would not set it automatic to performance. Let the user be responsible for it. But that's my opinion. @Hikandy You are correct this stuff is all unrelated to your issue. |
My settings are sadly not respected either. Turbo is set to never but it turns on all the time when a charger is plugged in.
Debug output:
|
Can you confirm if this is related to: #398 |
@AdnanHodzic Pretty sure this is a different issue. I'm also on intel, not amd. |
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. In meantime closing the issue due to inactivity. |
Here is my debug output
`Using settings defined in /etc/auto-cpufreq.conf file
Linux distro: Arch Linux
Linux kernel: 5.16.1-arch1-g14-2
Processor: AMD Ryzen 7 5800U with Radeon Graphics
Cores: 16
Architecture: x86_64
Driver: amd-pstate
------------------------------ Current CPU stats ------------------------------
CPU max frequency: 1901 MHz
CPU min frequency: 1600 MHz
Core Usage Temperature Frequency
CPU0: 0.0% 37 °C 1600 MHz
CPU1: 0.0% 37 °C 1600 MHz
CPU2: 0.0% 37 °C 1600 MHz
CPU3: 0.0% 37 °C 1600 MHz
CPU4: 0.0% 37 °C 1600 MHz
CPU5: 0.0% 37 °C 1600 MHz
CPU6: 1.0% 37 °C 1600 MHz
CPU7: 0.0% 37 °C 1600 MHz
CPU8: 0.0% 37 °C 1600 MHz
CPU9: 1.0% 37 °C 1563 MHz
CPU10: 0.0% 37 °C 1600 MHz
CPU11: 1.0% 37 °C 1600 MHz
CPU12: 0.0% 37 °C 1600 MHz
CPU13: 0.0% 37 °C 1600 MHz
CPU14: 0.0% 37 °C 1600 MHz
CPU15: 0.0% 37 °C 1600 MHz
auto-cpufreq version: Version : 1.9.1-3
Python: 3.10.2
psutil package: 5.9.0
platform package: 1.0.8
click package: 8.0.3
distro package: 1.6.0
Computer type: Notebook
Battery is: discharging
auto-cpufreq system resource consumption:
cpu usage: 0.0 %
memory use: 0.15 %
Total CPU usage: 0.9 %
Total system load: 0.94
Average temp. of all cores: 37.125 °C
Currently using: powersave governor
Currently turbo boost is: off
`
this is my config file
`
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
1 │ # settings for when connected to a power source
2 │ [charger]
3 │ # see available governors by running: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
4 │ # preferred governor.
5 │ governor = performance
6 │
7 │ # minimum cpu frequency (in kHz)
8 │ # example: for 800 MHz = 800000 kHz --> scaling_min_freq = 800000
9 │ # see conversion info: https://www.rapidtables.com/convert/frequency/mhz-to-hz.html
10 │ # to use this feature, uncomment the following line and set the value accordingly
11 │ # scaling_min_freq = 800000
12 │
13 │ # maximum cpu frequency (in kHz)
14 │ # example: for 1GHz = 1000 MHz = 1000000 kHz -> scaling_max_freq = 1000000
15 │ # see conversion info: https://www.rapidtables.com/convert/frequency/mhz-to-hz.html
16 │ # to use this feature, uncomment the following line and set the value accordingly
17 │ # scaling_max_freq = 1000000
18 │
19 │ # turbo boost setting. possible values: always, auto, never
20 │ turbo = auto
21 │
22 │ # settings for when using battery power
23 │ [battery]
24 │ # see available governors by running: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
25 │ # preferred governor
26 │ governor = powersave
27 │
28 │ # minimum cpu frequency (in kHz)
29 │ # example: for 800 MHz = 800000 kHz --> scaling_min_freq = 800000
30 │ # see conversion info: https://www.rapidtables.com/convert/frequency/mhz-to-hz.html
31 │ # to use this feature, uncomment the following line and set the value accordingly
32 │ scaling_min_freq = 1600000
33 │
34 │ # maximum cpu frequency (in kHz)
35 │ # see conversion info: https://www.rapidtables.com/convert/frequency/mhz-to-hz.html
36 │ # example: for 1GHz = 1000 MHz = 1000000 kHz -> scaling_max_freq = 1000000
37 │ # to use this feature, uncomment the following line and set the value accordingly
38 │ scaling_max_freq = 3000000
39 │
40 │ # turbo boost setting. possible values: always, auto, never
41 │ turbo = auto
`
i want to set the max freq as 3ghz but its stuck at 1900
The text was updated successfully, but these errors were encountered: