All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
@ 2017-10-07 14:10 ` bugzilla-daemon
  2017-10-07 15:13 ` bugzilla-daemon
                   ` (9 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 14:10 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

Artem S. Tashkinov (t.artem@mailcity.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|intel_pstate                |cpufreq
           Assignee|kristen.c.accardi@intel.com |linux-pm@vger.kernel.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
  2017-10-07 14:10 ` [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo bugzilla-daemon
@ 2017-10-07 15:13 ` bugzilla-daemon
  2017-10-07 15:21 ` bugzilla-daemon
                   ` (8 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 15:13 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

Doug Smythies (dsmythies@telus.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsmythies@telus.net

--- Comment #1 from Doug Smythies (dsmythies@telus.net) ---
this is a duplicate of bug #197009.
the change was intentional.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
  2017-10-07 14:10 ` [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo bugzilla-daemon
  2017-10-07 15:13 ` bugzilla-daemon
@ 2017-10-07 15:21 ` bugzilla-daemon
  2017-10-07 15:41 ` bugzilla-daemon
                   ` (7 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 15:21 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

Artem S. Tashkinov (t.artem@mailcity.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |torvalds@linux-foundation.o
                   |                            |rg

--- Comment #2 from Artem S. Tashkinov (t.artem@mailcity.com) ---
This breaks a lot of user space applications which report frequencies.

CC'ing Linus Torvalds.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (2 preceding siblings ...)
  2017-10-07 15:21 ` bugzilla-daemon
@ 2017-10-07 15:41 ` bugzilla-daemon
  2017-10-07 15:53 ` bugzilla-daemon
                   ` (6 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 15:41 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

--- Comment #3 from Doug Smythies (dsmythies@telus.net) ---
Back on bug #197009, I couldn't find the related e-mail thread. Now I did:
https://marc.info/?t=149766883400002&r=1&w=2

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (3 preceding siblings ...)
  2017-10-07 15:41 ` bugzilla-daemon
@ 2017-10-07 15:53 ` bugzilla-daemon
  2017-10-07 15:57 ` bugzilla-daemon
                   ` (5 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 15:53 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

Artem S. Tashkinov (t.artem@mailcity.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lenb@kernel.org

--- Comment #4 from Artem S. Tashkinov (t.artem@mailcity.com) ---
(In reply to Doug Smythies from comment #3)
> Back on bug #197009, I couldn't find the related e-mail thread. Now I did:
> https://marc.info/?t=149766883400002&r=1&w=2

Thanks!

> Users who have been consulting /proc/cpuinfo to
> track changing CPU frequency will be dissapointed that
> it no longer wiggles -- perhaps being unaware of the
> limitations of the information they have been consuming.
> 
> Yes, they can change their scripts to look in sysfs
> cpufreq/scaling_cur_frequency.  Here they will find the same
> data of dubious quality here removed from /proc/cpuinfo.
> The value in sysfs will be addressed in a subsequent patch
> to address issues 1-3, above.
> 
> Issue 4 will remain -- users that really care about
> accurate frequency information should not be using either
> proc or sysfs kernel interfaces.
> They should be using using turbostat(8), or a similar
> purpose-built analysis tool.

That sounds like a dozen of Linux utilities need to be rewritten to either
include the turbostat source (how do you even see that? what about updates to
this code?) or ... Len Brown has some other ideas in mind? Does turbostat work
without insmod()'ing the msr module first? Most distros don't autopreload it.

You break the user space interfaces and don't offer any realistic alternatives
at all. I for one refuse to run turbostat in console just to know what
frequencies my CPU cores are running at.

This is not how it should work.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (4 preceding siblings ...)
  2017-10-07 15:53 ` bugzilla-daemon
@ 2017-10-07 15:57 ` bugzilla-daemon
  2017-10-07 16:02 ` bugzilla-daemon
                   ` (4 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 15:57 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

Artem S. Tashkinov (t.artem@mailcity.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|4.13.4-200.fc26.x86_64      |4.13

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (5 preceding siblings ...)
  2017-10-07 15:57 ` bugzilla-daemon
@ 2017-10-07 16:02 ` bugzilla-daemon
  2017-10-07 22:33 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 16:02 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

--- Comment #5 from Artem S. Tashkinov (t.artem@mailcity.com) ---
While we're at it I don't understand why I see four different values at 

/sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq

My CPU has just two physical cores (the two others are HT). I'm OK with Value0
Value0 and Value1 Value1 but not with four different values. I understand that
frequencies are dynamic but not that dynamic so that the cat utility which
completes in under 0.001 seconds could see four quite different values.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (6 preceding siblings ...)
  2017-10-07 16:02 ` bugzilla-daemon
@ 2017-10-07 22:33 ` bugzilla-daemon
  2017-10-08  3:37 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-07 22:33 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

--- Comment #6 from Artem S. Tashkinov (t.artem@mailcity.com) ---
The /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq interface is also
broken in 4.13.

This one liner:

cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq | awk '{if (max<$0)
max=$0}END{printf "%.2fGHz",max/1000000}'

prints values from 0.50GHz to 2.55GHz even though my laptop is more or less
completely idle (no running applications aside from XFCE itself).

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (7 preceding siblings ...)
  2017-10-07 22:33 ` bugzilla-daemon
@ 2017-10-08  3:37 ` bugzilla-daemon
  2017-10-11  5:49 ` bugzilla-daemon
  2017-10-16 22:51 ` bugzilla-daemon
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-08  3:37 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

--- Comment #7 from Doug Smythies (dsmythies@telus.net) ---
@Artem: Please be considerate that, since this bug is unassigned, emails are
going to the entire linux-pm e-mail list.

> The /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq interface is also
> broken in 4.13.

It is not broken, and the numbers you are getting are most probably correct.
If you are running a desktop computer with a GUI, then this statement:

"my laptop is more or less completely idle"

simply is not true. You would have to disable the GUI and a bunch of other
services to get a more idle system (which would still not be completely idle).

If I use my test Ubuntu 16.04.3 server (no GUI) and disable several services,
i.e.:

$ cat set_cpu_turn_off_services
#! /bin/bash
# Turn off some services to try to get "idle" to be more "idle"
sudo systemctl stop mysql.service
sudo systemctl stop apache2.service
sudo systemctl stop nmbd.service
sudo systemctl stop smbd.service
sudo systemctl stop cron.service
sudo systemctl stop winbind.service
sudo systemctl stop apt-daily.timer

then for your command I usually get 1.61 GHz, which is the minimum for my
processor.

In order to not influence the system I was testing, I ran your command at a
very slow rate of once every 2 seconds for 6112 samples. 5970 (97.68%) of them
reported the minimum frequency for my 8 CPU processor.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (8 preceding siblings ...)
  2017-10-08  3:37 ` bugzilla-daemon
@ 2017-10-11  5:49 ` bugzilla-daemon
  2017-10-16 22:51 ` bugzilla-daemon
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-11  5:49 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

Zhang Rui (rui.zhang@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |haleakalas@yahoo.com

--- Comment #8 from Zhang Rui (rui.zhang@intel.com) ---
*** Bug 197017 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
       [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
                   ` (9 preceding siblings ...)
  2017-10-11  5:49 ` bugzilla-daemon
@ 2017-10-16 22:51 ` bugzilla-daemon
  10 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2017-10-16 22:51 UTC (permalink / raw)
  To: linux-pm

https://bugzilla.kernel.org/show_bug.cgi?id=197153

Len Brown (lenb@kernel.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|linux-pm@vger.kernel.org    |lenb@kernel.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2017-10-16 22:51 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-197153-137361@https.bugzilla.kernel.org/>
2017-10-07 14:10 ` [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo bugzilla-daemon
2017-10-07 15:13 ` bugzilla-daemon
2017-10-07 15:21 ` bugzilla-daemon
2017-10-07 15:41 ` bugzilla-daemon
2017-10-07 15:53 ` bugzilla-daemon
2017-10-07 15:57 ` bugzilla-daemon
2017-10-07 16:02 ` bugzilla-daemon
2017-10-07 22:33 ` bugzilla-daemon
2017-10-08  3:37 ` bugzilla-daemon
2017-10-11  5:49 ` bugzilla-daemon
2017-10-16 22:51 ` bugzilla-daemon

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.