I was hesitating a bit, but apparently this bug has been fixed, conservative is now considered a "dynamic" cpufreq policy.
I was hesitating a bit, but apparently this bug has been fixed, conservative is now considered a "dynamic" cpufreq policy.