On 4 July 2013 22:12, Toralf Förster <toralf.foerster@xxxxxx> wrote: > On 07/04/2013 10:23 AM, Viresh Kumar wrote: >> Ok, I did a mistake here (Thanks Srivatsa for telling me), this wasn't >> there in 3.10 but 3.11-rc1 >> >>> > c28375583b6471c1cb833a628ab6afb5b69079d0 >>> > >>> > They are touching ondemand governor and this may be creating some >>> > problems. But I am not sure about it, I must admit. >> So just try reverting about commit. >> >> In case you are using acpi-cpufreq driver, please try reverting this before >> above one: >> >> 8673b83bf2f013379453b4779047bf3c6ae387e4 > I reverted 8673b83b on top of 3.10.0 - no success, then I reverted > c2837558 too - no success. I assume that you have applied the patch given by Srivatsa earlier over these reverts? In that case you can go for a revert I believe. There aren't many cpufreq patches between 3.10 and the commit where you tested successfully earlier. But I now also suspect that this might have been caused by something outside cpufreq. -- 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
