Re: 3.10-rcX: cpu governor ondemand doesn't scale well after s2ram

["Toralf Förster" <toralf.foerster@gmx.de>]

On 07/04/2013 09:58 AM, Viresh Kumar wrote:
> On 4 July 2013 12:38, Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> 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).
> 
> Exactly!!
> 

Problem : yesterday I wasn't even able to 100% validate the issue at
commit a66b2e5 + f51e1eb just b/c there's another issue which
erratically happens here: sometimes cpu0 is too (not only cpu 1-3). In
that case the frequency are set to 2.6 GHz for each coret instead of 800
MHz for cpu0 and 2.601 GHz for cpu 1-3.

Furthermore I've the strong feeling, that the plugged in USB devices
might have an effect. And in the mean while I would not even exclude the
influence of the type of the 4 BOINC tasks (Asteorid@Home versus
Einstein@Home / World Community Grid which I have to run with nice -19
in the back ground) at the bisect results.

So all my ongoing attempts to bisect weren't successful till now.

I just tested the latest git tree from today (v3.10-8615-g23e3a1d) -
although f51e1eb is merged - the origin issue (cpu 1-3 set to 2.601 GHz
after wakeup) is still here.


-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3