On 13-12-18, 01:58, Stephen Boyd wrote: > BTW, Viresh, I see a lockdep splat when cpufreq_init returns an error > upon bringing the policy online the second time. I guess cpufreq_stats > aren't able to be freed from there because they take locks in different > order vs. the normal path?
Please share the lockdep report and the steps to reproduce it. I will see if I can simulate the failure forcefully.. -- viresh
