Re: Problem with cpufreq and i5 since post 3.9.0

2013-12-27 Thread David Woodfall

On (28/12/13 01:50), Rafael J. Wysocki  put forth the 
proposition:

CC: +Viresh and linux-pm

On Saturday, December 28, 2013 12:09:01 AM David Woodfall wrote:

On (27/12/13 19:53), Dave Woodfall  put forth the 
proposition:
>On (27/12/13 20:44), Heinz Diehl  put forth the 
proposition:
>>On 27.12.2013, David Woodfall wrote:
>>
>>>But any of the newer kernel versions I've tested only give me
>>>performance and powersave.
>>
>>I don't use any Fedora kernel, so I can't tell which governors are
>>enabled in those. You should check the value of "CONFIG_CPU_FREQ_GOV"
>>in the respective .config file for your installed kernel.
>>
>>In short: It seems that only "performance" and "powersave" are
>>compiled in.
>
>No, I used the same .config in all versions that I tested. I've also
>tried setting them as modules rather than built-in. This is the stock
>slackware .config:
>
>CONFIG_CPU_FREQ=y
>CONFIG_CPU_FREQ_TABLE=m
>CONFIG_CPU_FREQ_GOV_COMMON=y
>CONFIG_CPU_FREQ_STAT=m
>CONFIG_CPU_FREQ_STAT_DETAILS=y
># CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
>CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
># CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
># CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
>CONFIG_CPU_FREQ_GOV_PERFORMANCE=m
>CONFIG_CPU_FREQ_GOV_POWERSAVE=m
>CONFIG_CPU_FREQ_GOV_USERSPACE=y
>CONFIG_CPU_FREQ_GOV_ONDEMAND=m
>CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
>
>And modprobing any governor module does not change the output of
>scaling_available_governors.
>
>-Dave

I'm also experiencing this with a Intel G640 dual core machine.
Exactly the same effect.


Do you have CONFIG_X86_INTEL_PSTATE set?


I did and unsetting it solves the problem.

Thanks for that pointer.

-Dave


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Problem with cpufreq and i5 since post 3.9.0

2013-12-27 Thread David Woodfall

On (27/12/13 19:53), Dave Woodfall  put forth the 
proposition:

On (27/12/13 20:44), Heinz Diehl  put forth the 
proposition:

On 27.12.2013, David Woodfall wrote:


But any of the newer kernel versions I've tested only give me
performance and powersave.


I don't use any Fedora kernel, so I can't tell which governors are
enabled in those. You should check the value of "CONFIG_CPU_FREQ_GOV"
in the respective .config file for your installed kernel.

In short: It seems that only "performance" and "powersave" are
compiled in.


No, I used the same .config in all versions that I tested. I've also
tried setting them as modules rather than built-in. This is the stock
slackware .config:

CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=m
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

And modprobing any governor module does not change the output of 
scaling_available_governors.


-Dave


I'm also experiencing this with a Intel G640 dual core machine.
Exactly the same effect.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Problem with cpufreq and i5 since post 3.9.0

2013-12-27 Thread David Woodfall

On (27/12/13 20:44), Heinz Diehl  put forth the 
proposition:

On 27.12.2013, David Woodfall wrote:


But any of the newer kernel versions I've tested only give me
performance and powersave.


I don't use any Fedora kernel, so I can't tell which governors are
enabled in those. You should check the value of "CONFIG_CPU_FREQ_GOV"
in the respective .config file for your installed kernel.

In short: It seems that only "performance" and "powersave" are
compiled in.


No, I used the same .config in all versions that I tested. I've also
tried setting them as modules rather than built-in. This is the stock
slackware .config:

CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=m
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

And modprobing any governor module does not change the output of 
scaling_available_governors.


-Dave



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Problem with cpufreq and i5 since post 3.9.0

2013-12-27 Thread David Woodfall

I recently upgraded from 3.9.0 to 3.10.17 and found that I don't have
the same cpufreq governors available. I also tested with 3.12.6 and
3.13.0_rc5 with the same results.

3.9.0 tells me:
cat /sys/devices/system/cpu/*/cpufreq/scaling_available_governors
conservative ondemand powersave userspace performance
conservative ondemand powersave userspace performance
conservative ondemand powersave userspace performance
conservative ondemand powersave userspace performance

But any of the newer kernel versions I've tested only give me
performance and powersave.

I have selected userspace as default governor and all other governors
as built-in on all versions.

I need to either be able to use performance or use userspace and set 
for the max frequency. This is for an old application that tries to
detect cpu speed, but fails because it is from the days before 
scaling.


Can anyone tell me what I need to do with these newer kernels?

Regards

-Dave



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/