Re: cpuinfo_cur_freq always max

2007-12-18 Thread Stephen Clark
Johannes Weiner wrote: Hi, Stephen Clark <[EMAIL PROTECTED]> writes: userspace Please supply the full dmesg output on the non-working kernel the corresponding .config (or /proc/config.gz). Added Dave to CC. Hannes Duh - I rebooted into the new kernel and no longer see

Re: cpuinfo_cur_freq always max

2007-12-18 Thread Johannes Weiner
Hi, Stephen Clark <[EMAIL PROTECTED]> writes: > userspace Please supply the full dmesg output on the non-working kernel the corresponding .config (or /proc/config.gz). Added Dave to CC. Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: cpuinfo_cur_freq always max

2007-12-18 Thread Stephen Clark
Johannes Weiner wrote: Hi, Stephen Clark <[EMAIL PROTECTED]> writes: Which governor are you using? ondemand? Not sure - but the only thing that is changed is the kernel - if I go back to 2.6.23.1 it works correctly. Have a look at

Re: cpuinfo_cur_freq always max

2007-12-18 Thread Stephen Clark
Johannes Weiner wrote: Hi, Stephen Clark [EMAIL PROTECTED] writes: Which governor are you using? ondemand? Not sure - but the only thing that is changed is the kernel - if I go back to 2.6.23.1 it works correctly. Have a look at

Re: cpuinfo_cur_freq always max

2007-12-18 Thread Johannes Weiner
Hi, Stephen Clark [EMAIL PROTECTED] writes: userspace Please supply the full dmesg output on the non-working kernel the corresponding .config (or /proc/config.gz). Added Dave to CC. Hannes -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a

Re: cpuinfo_cur_freq always max

2007-12-18 Thread Stephen Clark
Johannes Weiner wrote: Hi, Stephen Clark [EMAIL PROTECTED] writes: userspace Please supply the full dmesg output on the non-working kernel the corresponding .config (or /proc/config.gz). Added Dave to CC. Hannes Duh - I rebooted into the new kernel and no longer see

Re: cpuinfo_cur_freq always max

2007-12-17 Thread Johannes Weiner
Hi, Stephen Clark <[EMAIL PROTECTED]> writes: >>Which governor are you using? ondemand? > Not sure - but the only thing that is changed is the kernel - if I go > back to 2.6.23.1 it works correctly. Have a look at /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor Hannes PS:

Re: cpuinfo_cur_freq always max

2007-12-17 Thread Johannes Weiner
Hi Steve, Stephen Clark <[EMAIL PROTECTED]> writes: > But with 2.6.23.8-34.fc7 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq > is always the max cpu speed of 1826000. > > While cpuinfo_cur_freq is the max 1826000 /proc/cpuinfo relflects the > correct speed when idle of > 996000 Which

cpuinfo_cur_freq always max

2007-12-17 Thread Stephen Clark
Hello, Running linux 2.6.23.1-21.fc7 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq correctly reflects the cpu speed, when idle it is 996000 and when compiling it is 1826000. Its also the same as what is in /proc/cpuinfo. But with 2.6.23.8-34.fc7

cpuinfo_cur_freq always max

2007-12-17 Thread Stephen Clark
Hello, Running linux 2.6.23.1-21.fc7 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq correctly reflects the cpu speed, when idle it is 996000 and when compiling it is 1826000. Its also the same as what is in /proc/cpuinfo. But with 2.6.23.8-34.fc7

Re: cpuinfo_cur_freq always max

2007-12-17 Thread Johannes Weiner
Hi Steve, Stephen Clark [EMAIL PROTECTED] writes: But with 2.6.23.8-34.fc7 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq is always the max cpu speed of 1826000. While cpuinfo_cur_freq is the max 1826000 /proc/cpuinfo relflects the correct speed when idle of 996000 Which governor

Re: cpuinfo_cur_freq always max

2007-12-17 Thread Johannes Weiner
Hi, Stephen Clark [EMAIL PROTECTED] writes: Which governor are you using? ondemand? Not sure - but the only thing that is changed is the kernel - if I go back to 2.6.23.1 it works correctly. Have a look at /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor Hannes PS: Steve,