On 24 April 2014 15:26, Meelis Roos <mroos@xxxxxxxx> wrote: > This is VIA EPIA board with 533 MHz VIA Samuel 2 CPU. Normally, longhaul > is not enabled automatically but with longhaul.enable=1. It used to work > up to 3.14 but in 3.15-rc, different cpufreq-related codepaths block for > long times and cause warnings. > > /usr/bin/cpufreq-set --cpu 0 --governor ondemand > is running since boot and hangs in D state. > Running cpufreq-info seems to just hang too. Okay, I know WTF is going on here. My mistake, but as I said earlier this patch only highlighted the issue by serializing things its there since last 6-8 months. I will send out patches shortly, please test them. Description of what actually happened will be present there in details. In short, we are sending double notifications here, once from core and once from driver :( -- 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
