On 07/04/2013 12:31 PM, Viresh Kumar wrote: > On 4 July 2013 12:25, Srivatsa S. Bhat <srivatsa.bhat@xxxxxxxxxxxxxxxxxx> wrote: >> On 07/04/2013 01:16 AM, Toralf Förster wrote: >>> On 06/30/2013 07:05 PM, Toralf Förster wrote: >>>> On 06/30/2013 06:33 PM, Srivatsa S. Bhat wrote: >>>>> Toralf, can you please >>>>> try out the below patch and see if it improves anything? (Don't revert anything, >>>>> just apply the below diff on a problematic kernel and see if it solves your >>>>> issue). >>>> >>>> applied on top of a66b2e5 - issue went away (either fixed or hidden now) >>>> >>>> Thx >>>> >>> But if I do apply that patch on top of kernel 3.10 then it has no effect >>> - 3.10 shows the same issue. >>> >> >> Weird. So I think something *else* got broken by some other patch, _after_ >> a66b2e5. Viresh, do you have any suspect commits in mind? > > If I was God I could have. But as I am a poor human being I > need more details (preferably with git bisect) :) > Haha :) 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). Regards, Srivatsa S. Bhat -- 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
