On 05/30/2013 08:41 AM, Viresh Kumar wrote:
Reverting this commit from v3.10-rc3 fixed the problem.
This is using the acpi-cpufreq driver -- there doesn't seem to be any way to
set the Intel P-state driver to performance by default.
This patch was pretty much sensible and all drivers now depend on it
now.
@Dirk: Can you please help us in understanding why this might be
happening. I believe it has to do with some bad design of acpi-cpufreq
driver (I tried to look into target routine but couldn't understand why
this might be happening).
Not really sorry I don't know any thing about acpi-cpufreq.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
