On 09/11/2013 12:42 PM, Srivatsa S. Bhat wrote: ... > OK, I took a second look at the code, and I suspect that applying the > second patch might help. So can you try by applying both the patches > please[1][2]? > ... > [1]. http://marc.info/?l=linux-kernel&m=137889516210816&w=2 > [2]. http://marc.info/?l=linux-kernel&m=137889800511940&w=2 Yes, with both of those patches applies, the problem is solved:-) I was going to test the second patch originally, but it sounded like it was more of a cleanup rather than a fix for my issue, so I didn't bother when I found the problem wasn't solved by patch 1. Sorry! For the record, I'm testing on a 2-CPU system, so I'm not sure whether your explanation applies; it talks about CPUs 2 and 3 whereas I only have CPUs 0 and 1, but perhaps your explanation applies equally to any pair of CPUs? For the record, here's the information you requested in the other email: # cat /sys/devices/system/cpu/cpu*/cpufreq/related_cpus 0 1 0 1 -- 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
