yarda
commented
3 days ago 1) WARNING tuned.plugins.plugin_cpu: unable to run x86_energy_perf_policy tool, ignoring CPU energy performance bias, is the tool installed?
Is the ' x86_energy_perf_policy' tool installed? It's usually in the kernel-tools package and is built from the kernel sources.
2) Do you not support NVMe controllers in Ubuntu: INFO tuned.plugins.base: instance disk: assigning devices sda, loop7, loop3, loop2, sdc, loop1, loop4, dm-0, loop9, dm-3, dm-1, loop8, loop6, dm-2, loop0, sdb, loop5
NVMe should be supported, could you provide output of:
$ udevadm info /dev/YOUR_NVME_DEVICE3) ERROR tuned.plugins.plugin_sysctl: Failed to read sysctl parameter 'kernel.sched_min_granularity_ns', the parameter does not exist 4) ERROR tuned.plugins.plugin_sysctl: Failed to read sysctl parameter 'kernel.sched_wakeup_granularity_ns', the parameter does not exist
Which TuneD profile triggers it? Recent upstream TuneD profiles use scheduler plugin, not sysctl plugin and it shouldn't trigger this error with recent kernels, e.g.:
[scheduler]
sched_latency_ns=60000000
sched_migration_cost_ns=500000
sched_min_granularity_ns=15000000
sched_wakeup_granularity_ns=2000000
stevefxp1
Hello all,
I am seeing some warning and error messages in my TuneD log. What do these mean and should I be concerned:
1) WARNING tuned.plugins.plugin_cpu: unable to run x86_energy_perf_policy tool, ignoring CPU energy performance bias, is the tool installed? 2) Do you not support NVMe controllers in Ubuntu: INFO tuned.plugins.base: instance disk: assigning devices sda, loop7, loop3, loop2, sdc, loop1, loop4, dm-0, loop9, dm-3, dm-1, loop8, loop6, dm-2, loop0, sdb, loop5 3) ERROR tuned.plugins.plugin_sysctl: Failed to read sysctl parameter 'kernel.sched_min_granularity_ns', the parameter does not exist 4) ERROR tuned.plugins.plugin_sysctl: Failed to read sysctl parameter 'kernel.sched_wakeup_granularity_ns', the parameter does not exist
Thanks, Steve