On 4 July 2013 13:34, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > On 4 July 2013 12:38, Srivatsa S. Bhat <srivatsa.bhat@xxxxxxxxxxxxxxxxxx> wrote: >> Coming to git bisect, I think it needs to be done between a66b2e5 + this-patch >> and 3.10 + this-patch, to ensure that we look for problematic commits in-between >> a66b2e5 and 3.10 (to avoid the bisect result ending up at a66b2e5 again). > > Toralf, > > Try reverting these patches in the order specified (revert both) > 419e172145cf6c51d436a8bf4afcd17511f0ff79 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 It is playing with how frequencies are reported and may be the culprit. -- 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
