Tuned issue

Hi,

I’ve been using tuned to set CPU speed for a few weeks. I started using it on Fedora 40 Workstation and everything worked as expected. Goal: low latency for audio.

However on dec 5, something happened and it stopped setting it like I wanted.

Yesterday, I upgraded to F41 and noticed that fact. So it’s not a F41 issue, it’s a tuned issue or something else causing it.

2024-12-13 08:19:41,775 INFO     tuned.daemon.application: TuneD: 2.24.1, kernel: 6.6.64-200.fc41.x86_64
2024-12-13 08:19:41,776 INFO     tuned.daemon.application: dynamic tuning is globally disabled
2024-12-13 08:19:41,787 INFO     tuned.daemon.daemon: using sleep interval of 1 second(s)
2024-12-13 08:19:41,789 INFO     tuned.profiles.loader: loading profile: latency-performance
2024-12-13 08:19:41,793 INFO     tuned.daemon.controller: starting controller
2024-12-13 08:19:41,793 INFO     tuned.daemon.daemon: starting tuning
2024-12-13 08:19:41,800 INFO     tuned.plugins.base: instance cpu: assigning devices cpu2, cpu1, cpu3, cpu0
2024-12-13 08:19:41,801 INFO     tuned.plugins.plugin_cpu: We are running on an x86 AuthenticAMD platform
2024-12-13 08:19:41,804 WARNING  tuned.plugins.base: instance video: no matching devices available
2024-12-13 08:19:41,806 INFO     tuned.plugins.plugin_cpu: setting governor 'performance' on cpu 'cpu2'
2024-12-13 08:19:41,815 INFO     tuned.plugins.plugin_cpu: setting governor 'performance' on cpu 'cpu1'
2024-12-13 08:19:41,821 INFO     tuned.plugins.plugin_cpu: setting governor 'performance' on cpu 'cpu3'
2024-12-13 08:19:41,831 INFO     tuned.plugins.plugin_cpu: setting governor 'performance' on cpu 'cpu0'
2024-12-13 08:19:41,839 INFO     tuned.plugins.plugin_cpu: setting new cpu latency 3
2024-12-13 08:19:41,840 INFO     tuned.plugins.plugin_sysctl: reapplying system sysctl
2024-12-13 08:19:41,840 INFO     tuned.daemon.daemon: static tuning from profile 'latency-performance' applied
2024-12-13 08:19:50,658 INFO     tuned.daemon.daemon: stopping tuning
2024-12-13 08:19:50,659 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu2'
2024-12-13 08:19:50,659 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu1'
2024-12-13 08:19:50,659 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu3'
2024-12-13 08:19:50,659 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu0'
2024-12-13 08:19:50,660 INFO     tuned.profiles.loader: loading profile: balanced
2024-12-13 08:19:50,661 INFO     tuned.daemon.daemon: starting tuning
2024-12-13 08:19:50,707 INFO     tuned.daemon.daemon: stopping tuning
2024-12-13 08:19:50,712 INFO     tuned.plugins.base: instance audio: assigning devices snd_hda_intel
2024-12-13 08:19:50,713 WARNING  tuned.plugins.base: instance video: no matching devices available
2024-12-13 08:19:50,757 INFO     tuned.plugins.base: instance disk: assigning devices sda, loop9, loop14, loop6, loop12, loop5, loop15, loop7, loop13, dm-0, loop0, sdb, loop11, loop4, loop2, sdc, loop1, loop8, zram0, loop10, loop3
2024-12-13 08:19:50,773 INFO     tuned.plugins.base: instance scsi_host: assigning devices host5, host4, host2, host0, host1, host3
2024-12-13 08:19:50,774 INFO     tuned.plugins.base: instance cpu: assigning devices cpu2, cpu1, cpu3, cpu0
2024-12-13 08:19:50,775 INFO     tuned.plugins.plugin_cpu: We are running on an x86 AuthenticAMD platform
2024-12-13 08:19:50,791 ERROR    tuned.utils.commands: Executing 'modprobe -r cpufreq_conservative' error: modprobe: FATAL: Module cpufreq_conservative is builtin.
2024-12-13 08:19:50,795 INFO     tuned.plugins.plugin_scsi_host: ALPM control file ('/sys/class/scsi_host/host5/link_power_management_policy') not found, skipping ALPM setting for 'host5'
2024-12-13 08:19:50,795 INFO     tuned.plugins.plugin_scsi_host: ALPM control file ('/sys/class/scsi_host/host4/link_power_management_policy') not found, skipping ALPM setting for 'host4'
2024-12-13 08:19:50,796 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu2'
2024-12-13 08:19:50,802 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu1'
2024-12-13 08:19:50,808 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu3'
2024-12-13 08:19:50,812 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu0'
2024-12-13 08:19:50,819 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu2'
2024-12-13 08:19:50,819 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu1'
2024-12-13 08:19:50,819 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu3'
2024-12-13 08:19:50,819 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu0'
2024-12-13 08:19:50,820 INFO     tuned.daemon.daemon: static tuning from profile 'balanced' applied
2024-12-13 08:19:50,821 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu2'
2024-12-13 08:19:50,821 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu1'
2024-12-13 08:19:50,821 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu3'
2024-12-13 08:19:50,821 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu0'
2024-12-13 08:19:50,822 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu2'
2024-12-13 08:19:50,826 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu1'
2024-12-13 08:19:50,830 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu3'
2024-12-13 08:19:50,837 INFO     tuned.plugins.plugin_cpu: setting governor 'schedutil' on cpu 'cpu0'
2024-12-13 08:19:50,845 INFO     tuned.profiles.loader: loading profile: balanced
2024-12-13 08:19:50,846 INFO     tuned.daemon.daemon: starting tuning
2024-12-13 08:19:50,848 INFO     tuned.plugins.base: instance audio: assigning devices snd_hda_intel
2024-12-13 08:19:50,849 WARNING  tuned.plugins.base: instance video: no matching devices available
2024-12-13 08:19:50,860 INFO     tuned.plugins.base: instance disk: assigning devices sda, loop9, loop14, loop6, loop12, loop5, loop15, loop7, loop13, dm-0, loop0, sdb, loop11, loop4, loop2, sdc, loop1, loop8, zram0, loop10, loop3
2024-12-13 08:19:50,864 INFO     tuned.plugins.base: instance scsi_host: assigning devices host5, host4, host2, host0, host1, host3
2024-12-13 08:19:50,865 INFO     tuned.plugins.base: instance cpu: assigning devices cpu2, cpu1, cpu3, cpu0
2024-12-13 08:19:50,866 INFO     tuned.plugins.plugin_cpu: We are running on an x86 AuthenticAMD platform
2024-12-13 08:19:50,876 ERROR    tuned.utils.commands: Executing 'modprobe -r cpufreq_conservative' error: modprobe: FATAL: Module cpufreq_conservative is builtin.
2024-12-13 08:19:50,881 INFO     tuned.plugins.plugin_scsi_host: ALPM control file ('/sys/class/scsi_host/host5/link_power_management_policy') not found, skipping ALPM setting for 'host5'
2024-12-13 08:19:50,881 INFO     tuned.plugins.plugin_scsi_host: ALPM control file ('/sys/class/scsi_host/host4/link_power_management_policy') not found, skipping ALPM setting for 'host4'
2024-12-13 08:19:50,882 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu2'
2024-12-13 08:19:50,887 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu1'
2024-12-13 08:19:50,892 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu3'
2024-12-13 08:19:50,899 INFO     tuned.plugins.plugin_cpu: setting governor 'conservative' on cpu 'cpu0'
2024-12-13 08:19:50,904 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu2'
2024-12-13 08:19:50,904 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu1'
2024-12-13 08:19:50,905 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu3'
2024-12-13 08:19:50,905 INFO     tuned.plugins.plugin_cpu: Setting boost value '1' for cpu 'cpu0'
2024-12-13 08:19:50,905 INFO     tuned.daemon.daemon: static tuning from profile 'balanced' applied



So, to minimise latency, I now need to set it manually with sudo tuned-adm profile latency-performance because, as one can see in the log, it doesn’t stick anymore. How to diagnose and fix?

Well, apparently there was an update to gnome on dec 5 2024 that fucked up existing power settings. Fixed (hopefully) by following this method and opening the gnome power settings and setting it to performance from there!

Doing it from the CLI doesn’t seem to be enough anymore.

Source: Tuned vs Settings --> Tuned wins by K.O

The eternal CLI GUI conflict…

1 Like

That’s why I remove tuned :stuck_out_tongue:

My hardware power-saves however the firmware determines it from the MFG without OS concern, and I force CPU MSRs directly for power states with the simplicity of AC = max performance and BAT = balance (x86_energy_perf_policy + udev)