/etc/init.d/ondemand tries to set the governor to ondemand unconditionally, even on intel systems with p-state.
Systems with the p-state frequency scaling do not have an ondemand governor at all. This means that the /etc/init.d/ondemand falls back to the powersave governor, hindering performance.
Alltogether, the /etc/init.d/ondemand looks hackish. Its operation relies on assumptions on the system setup that are just plain wrong:
1) That one does not install the cpufreq utils
since, as mentioned in the original bug report, it destroys the work of /etc/init.d/cpufrequtils
2) That one is on the acpi cpu frequency driver
since it is hardwired with the governors provided by such driver.
I strongly recommend getting rid of /etc/init.d/ondemand
There is another issue:
/etc/init. d/ondemand tries to set the governor to ondemand unconditionally, even on intel systems with p-state.
Systems with the p-state frequency scaling do not have an ondemand governor at all. This means that the /etc/init. d/ondemand falls back to the powersave governor, hindering performance.
Alltogether, the /etc/init. d/ondemand looks hackish. Its operation relies on assumptions on the system setup that are just plain wrong:
1) That one does not install the cpufreq utils d/cpufrequtils
since, as mentioned in the original bug report, it destroys the work of /etc/init.
2) That one is on the acpi cpu frequency driver
since it is hardwired with the governors provided by such driver.
I strongly recommend getting rid of /etc/init. d/ondemand