On 25/05/16 19:51, Dmitry Osipenko wrote:
On 25.05.2016 18:09, Jon Hunter wrote:
If you are able to reproduce this on v3.18, then it would be good if you
could trace the CCF calls around this WARNING to see what is causing the
I managed to reproduce it with some CCF "tracing".
Full kmsg log is here: https://bpaste.net/show/d8ab7b7534b7
Looks like CPU freq governor thread yields during clk_set_rate() and
then CPU idle kicks in, taking the same mutex.
On the surface that sounds odd to me, but without understanding the
details, I guess I don't know if this is a valid thing to be doing or
even how that actually works!
However, cpufreq_interactive governor is android specific governor and
isn't in upstream kernel yet. Quick googling shows that recent
"upstreaming" patch uses same cpufreq_interactive_speedchange_task:
Do you know if this version they are upstreaming could also yield during
I'm not aware of other possibility to reproduce this issue, it needs
some CCF interaction from a separate task. So the current upstream
kernel shouldn't be affected, I guess.
What still does not make sense to me is why any frequency changes have
not completed before we attempt to enter the LP2 state?
OK, well may be we will hold off on this change for the moment.