On 10/10/2014 07:30 AM, Viresh Kumar wrote:
On 10 October 2014 16:51, Prarit Bhargava prarit@redhat.com wrote:
Yep, I get that panic doing a very simple
#!/bin/bash
i=0 while [ True ]; do i=$((i+1)) echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor & echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor & echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor & echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor & if [ $((i % 100)) = 0 ]; then echo $i fi done
The blocking issue that I have (soon to be resolved I hope) is
http://marc.info/?l=linux-kernel&m=141286895623716&w=2
which is preventing me from doing any LOCKDEP analysis on this system.
I'm working on all of the above right now ...
I have updated my patchset a bit now, the new branch is: cpufreq/governor-fixes-v2. But have you tried this on 3.17 without my patches?
Yes, I unfortunately have a different set of issues with vanilla 3.17 (previously mentioned locking issue). I've done a quick and dirty hack to get around that, and everything seems okay.
I apply your patches and I get a panic the first time I read sysfs
P.
-- viresh