24 Mar
2013
24 Mar
'13
9:05 a.m.
[Forgot to add all in previous mail, reply-all now]
On 24 March 2013 00:20, Borislav Petkov bp@alien8.de wrote:
On Sat, Mar 23, 2013 at 10:34:28PM +0530, Viresh Kumar wrote:
And that is already caused recently?
Ahh!! s/already/also
3.8.3 is fine and there are no cpufreq patches in v3.8..v3.8.3. Which would mean, plain v3.8 is also fine. Which means, the breakage must've come in during the merge window.
I didn't get a complete picture of your problem, can you elaborate a bit with all your observations?
It might be related to the problem reported by Duncan and might be solved by the patch i sent yesterday.