* time_in_state on Ubuntu 13.10 @ 2014-04-28 14:43 Mascha Kurpicz 2014-04-29 4:28 ` Viresh Kumar 0 siblings, 1 reply; 7+ messages in thread From: Mascha Kurpicz @ 2014-04-28 14:43 UTC (permalink / raw) To: cpufreq; +Cc: Maxime Colmant Hi, First of all I would like to thank for the cpufreq utility that I use regularly. Unfortunately, when upgrading our systems from Ubuntu 12.04 to 13.10, we are encountering some issues with the data in /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state. On some of the machines, the values are all set to 0 [1], whereas on other machines, values are 0 or very small [2]. In both cases, the output of cpufreq-info for the cpufreq stats is not correct. When running Ubuntu 12.04, we get reasonable values. We noticed this behavior on Intel i3 machines, and on Intel Xeon. Kernel version in all cases is 3.11.0-20-generic. Thanks in advance and best regards, Mascha --- [1] user@ubuntu1310:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state 3100000 0 2800000 0 2600000 0 2400000 0 2200000 0 2000000 0 1800000 0 1600000 0 user@ubuntu1310:~$ cpufreq-info ... cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60 GHz:-nan% (21768) ... [2] user@ubuntu1310:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state 3100000 0 2800000 0 2600000 0 2400000 0 2200000 0 2000000 0 1800000 0 1600000 6 user@ubuntu1310:~$ cpufreq-info ... cpufreq stats: 3.10 GHz:0.00%, 2.80 GHz:0.00%, 2.60 GHz:0.00%, 2.40 GHz:0.00%, 2.20 GHz:0.00%, 2.00 GHz:0.00%, 1.80 GHz:0.00%, 1.60 GHz:100.00% (86356) ... ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: time_in_state on Ubuntu 13.10 2014-04-28 14:43 time_in_state on Ubuntu 13.10 Mascha Kurpicz @ 2014-04-29 4:28 ` Viresh Kumar 2014-04-29 7:17 ` Mascha Kurpicz 0 siblings, 1 reply; 7+ messages in thread From: Viresh Kumar @ 2014-04-29 4:28 UTC (permalink / raw) To: Mascha Kurpicz, Linux PM list, Rafael J. Wysocki Cc: cpufreq@vger.kernel.org, Maxime Colmant On Mon, Apr 28, 2014 at 8:13 PM, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: > First of all I would like to thank for the cpufreq utility that I use > regularly. > > Unfortunately, when upgrading our systems from Ubuntu 12.04 to 13.10, we > are encountering some issues with the data in > /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state. > > On some of the machines, the values are all set to 0 [1], whereas on > other machines, values are 0 or very small [2]. In both cases, the > output of cpufreq-info for the cpufreq stats is not correct. When > running Ubuntu 12.04, we get reasonable values. > > We noticed this behavior on Intel i3 machines, and on Intel Xeon. Kernel > version in all cases is 3.11.0-20-generic. Do you mean that kernel version is same for 12.04 and 13.10? We need kernel versions for these two bases. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: time_in_state on Ubuntu 13.10 2014-04-29 4:28 ` Viresh Kumar @ 2014-04-29 7:17 ` Mascha Kurpicz 2014-04-29 8:26 ` Viresh Kumar 0 siblings, 1 reply; 7+ messages in thread From: Mascha Kurpicz @ 2014-04-29 7:17 UTC (permalink / raw) To: Viresh Kumar, Linux PM list, Rafael J. Wysocki Cc: cpufreq@vger.kernel.org, Maxime Colmant Hi, Sorry for the imprecision. Works correctly with Ubuntu 12.04.3 LTS - kernel 3.2.0-29-generic Ubuntu 12.04.3 LTS - kernel 3.8.0-29 Ubuntu 13.10 - kernel 3.8.0-29-generic 0 or very small (e.g. 6) values with Ubuntu 13.10 - kernel 3.11.0-20-generic Thanks, Mascha On 04/29/2014 06:28 AM, Viresh Kumar wrote: > On Mon, Apr 28, 2014 at 8:13 PM, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: >> First of all I would like to thank for the cpufreq utility that I use >> regularly. >> >> Unfortunately, when upgrading our systems from Ubuntu 12.04 to 13.10, we >> are encountering some issues with the data in >> /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state. >> >> On some of the machines, the values are all set to 0 [1], whereas on >> other machines, values are 0 or very small [2]. In both cases, the >> output of cpufreq-info for the cpufreq stats is not correct. When >> running Ubuntu 12.04, we get reasonable values. >> >> We noticed this behavior on Intel i3 machines, and on Intel Xeon. Kernel >> version in all cases is 3.11.0-20-generic. > Do you mean that kernel version is same for 12.04 and 13.10? We need > kernel versions for these two bases. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: time_in_state on Ubuntu 13.10 2014-04-29 7:17 ` Mascha Kurpicz @ 2014-04-29 8:26 ` Viresh Kumar 2014-04-29 8:38 ` Mascha Kurpicz 0 siblings, 1 reply; 7+ messages in thread From: Viresh Kumar @ 2014-04-29 8:26 UTC (permalink / raw) To: Mascha Kurpicz Cc: Linux PM list, Rafael J. Wysocki, cpufreq@vger.kernel.org, Maxime Colmant On 29 April 2014 12:47, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: > Sorry for the imprecision. > > Works correctly with > Ubuntu 12.04.3 LTS - kernel 3.2.0-29-generic > Ubuntu 12.04.3 LTS - kernel 3.8.0-29 > Ubuntu 13.10 - kernel 3.8.0-29-generic > > 0 or very small (e.g. 6) values with > Ubuntu 13.10 - kernel 3.11.0-20-generic Can you provide cpufreq-info 's output for the last two cases please? i.e. > Ubuntu 13.10 - kernel 3.8.0-29-generic > Ubuntu 13.10 - kernel 3.11.0-20-generic ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: time_in_state on Ubuntu 13.10 2014-04-29 8:26 ` Viresh Kumar @ 2014-04-29 8:38 ` Mascha Kurpicz 2014-05-02 5:25 ` Viresh Kumar 0 siblings, 1 reply; 7+ messages in thread From: Mascha Kurpicz @ 2014-04-29 8:38 UTC (permalink / raw) To: Viresh Kumar Cc: Linux PM list, Rafael J. Wysocki, cpufreq@vger.kernel.org, Maxime Colmant On 04/29/2014 10:26 AM, Viresh Kumar wrote: > On 29 April 2014 12:47, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: >> Sorry for the imprecision. >> >> Works correctly with >> Ubuntu 12.04.3 LTS - kernel 3.2.0-29-generic >> Ubuntu 12.04.3 LTS - kernel 3.8.0-29 >> Ubuntu 13.10 - kernel 3.8.0-29-generic >> >> 0 or very small (e.g. 6) values with >> Ubuntu 13.10 - kernel 3.11.0-20-generic > Can you provide cpufreq-info 's output for the last two cases please? > > i.e. >> Ubuntu 13.10 - kernel 3.8.0-29-generic user@ubuntu1310:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:26.39%, 2.80 GHz:0.13%, 2.60 GHz:0.23%, 2.40 GHz:0.20%, 2.20 GHz:0.20%, 2.00 GHz:0.30%, 1.80 GHz:0.26%, 1.60 GHz:72.28% (1742) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:2.17%, 2.80 GHz:0.04%, 2.60 GHz:0.07%, 2.40 GHz:0.09%, 2.20 GHz:1.06%, 2.00 GHz:0.31%, 1.80 GHz:0.42%, 1.60 GHz:95.84% (2752) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:2.24%, 2.80 GHz:0.00%, 2.60 GHz:0.02%, 2.40 GHz:0.01%, 2.20 GHz:0.01%, 2.00 GHz:0.09%, 1.80 GHz:0.00%, 1.60 GHz:97.63% (431) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:1.49%, 2.80 GHz:0.00%, 2.60 GHz:0.03%, 2.40 GHz:0.03%, 2.20 GHz:0.01%, 2.00 GHz:0.01%, 1.80 GHz:0.01%, 1.60 GHz:98.43% (560) >> Ubuntu 13.10 - kernel 3.11.0-20-generic user@ubuntu1310:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60 GHz:-nan% (75) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60 GHz:-nan% (71) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60 GHz:-nan% (16) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 3.10 GHz available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60 GHz:-nan% (6) ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: time_in_state on Ubuntu 13.10 2014-04-29 8:38 ` Mascha Kurpicz @ 2014-05-02 5:25 ` Viresh Kumar 2014-05-05 12:08 ` Mascha Kurpicz 0 siblings, 1 reply; 7+ messages in thread From: Viresh Kumar @ 2014-05-02 5:25 UTC (permalink / raw) To: Mascha Kurpicz Cc: Linux PM list, Rafael J. Wysocki, cpufreq@vger.kernel.org, Maxime Colmant On 29 April 2014 14:08, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: > On 04/29/2014 10:26 AM, Viresh Kumar wrote: >> On 29 April 2014 12:47, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: >>> Sorry for the imprecision. >>> >>> Works correctly with >>> Ubuntu 12.04.3 LTS - kernel 3.2.0-29-generic >>> Ubuntu 12.04.3 LTS - kernel 3.8.0-29 >>> Ubuntu 13.10 - kernel 3.8.0-29-generic >>> >>> 0 or very small (e.g. 6) values with >>> Ubuntu 13.10 - kernel 3.11.0-20-generic >> Can you provide cpufreq-info 's output for the last two cases please? Sorry, got distracted and just forgot about this thread :), must have marked it in my pending list :( Anyways, I have tried to look at the diff between these kernel releases and looks like I couldn't figure out what's going wrong. I tried to test things with the latest kernel and they seem to be working fine. Atleast on my ARM board. Would it be possible for you to do a git bisect between 3.8 and 3.11 ? -- viresh ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: time_in_state on Ubuntu 13.10 2014-05-02 5:25 ` Viresh Kumar @ 2014-05-05 12:08 ` Mascha Kurpicz 0 siblings, 0 replies; 7+ messages in thread From: Mascha Kurpicz @ 2014-05-05 12:08 UTC (permalink / raw) To: Viresh Kumar Cc: Linux PM list, Rafael J. Wysocki, cpufreq@vger.kernel.org, Maxime Colmant On 05/02/2014 07:25 AM, Viresh Kumar wrote: > On 29 April 2014 14:08, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: >> On 04/29/2014 10:26 AM, Viresh Kumar wrote: >>> On 29 April 2014 12:47, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote: >>>> Sorry for the imprecision. >>>> >>>> Works correctly with >>>> Ubuntu 12.04.3 LTS - kernel 3.2.0-29-generic >>>> Ubuntu 12.04.3 LTS - kernel 3.8.0-29 >>>> Ubuntu 13.10 - kernel 3.8.0-29-generic >>>> >>>> 0 or very small (e.g. 6) values with >>>> Ubuntu 13.10 - kernel 3.11.0-20-generic >>> Can you provide cpufreq-info 's output for the last two cases please? > Sorry, got distracted and just forgot about this thread :), must have marked > it in my pending list :( > > Anyways, I have tried to look at the diff between these kernel releases and > looks like I couldn't figure out what's going wrong. > > I tried to test things with the latest kernel and they seem to be working fine. > Atleast on my ARM board. > > Would it be possible for you to do a git bisect between 3.8 and 3.11 ? We just tested with the latest release (14.04) and realized that the issue was already fixed for the latest kernel version, sorry about that! https://lkml.org/lkml/2013/9/7/119 Thanks anyways for your support :-) > -- > viresh ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-05-05 12:08 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-04-28 14:43 time_in_state on Ubuntu 13.10 Mascha Kurpicz 2014-04-29 4:28 ` Viresh Kumar 2014-04-29 7:17 ` Mascha Kurpicz 2014-04-29 8:26 ` Viresh Kumar 2014-04-29 8:38 ` Mascha Kurpicz 2014-05-02 5:25 ` Viresh Kumar 2014-05-05 12:08 ` Mascha Kurpicz
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox