Linux-PM Archive on lore.kernel.org
 help / color / Atom feed
* [Bug 206517] New: scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX
@ 2020-02-13 15:27 bugzilla-daemon
  2020-02-14  8:02 ` [Bug 206517] " bugzilla-daemon
  0 siblings, 1 reply; 2+ messages in thread
From: bugzilla-daemon @ 2020-02-13 15:27 UTC (permalink / raw)
  To: linux-pm

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

            Bug ID: 206517
           Summary: scaling_cur_freq very different from cpuinfo_cur_freq
                    on Acer Predator Helios 500 PH517-61-R0GX
           Product: Power Management
           Version: 2.5
    Kernel Version: 5.5.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: bero@lindev.ch
        Regression: No

On an Acer Predator Helios 500 PH517-61-R0GX, scaling_cur_freq values can vary
greatly from cpuinfo_cur_freq:

$ sudo cat /sys/devices/system/cpu/*/cpufreq/cpuinfo_cur_freq
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
3200000
$ cat /sys/devices/system/cpu/*/cpufreq/scaling_cur_freq 
548955
548955
548955
548955
548955
548955
548955
548955
548955
548955
548955
548955
548955
548955
548955
548955

Unfortunately, the performance I'm seeing on this box while compiling stuff
makes me think scaling_cur_freq is reporting correctly and cpuinfo_cur_freq is
telling lies.

This might be related to bug 203035

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

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

* [Bug 206517] scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX
  2020-02-13 15:27 [Bug 206517] New: scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX bugzilla-daemon
@ 2020-02-14  8:02 ` " bugzilla-daemon
  0 siblings, 0 replies; 2+ messages in thread
From: bugzilla-daemon @ 2020-02-14  8:02 UTC (permalink / raw)
  To: linux-pm

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

Thomas Renninger (trenn@suse.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |trenn@suse.de

--- Comment #1 from Thomas Renninger (trenn@suse.de) ---
Best use:
cpupower monitor

You can also measure workloads, e.g. when compiling something:

cpupower monitor make

Not sure what distro you are using and what the name of the package or whether
cpupower is packaged there... The sources, even it's userspace is part of the
kernel git repo:
tools/power/cpupower

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

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

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-13 15:27 [Bug 206517] New: scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX bugzilla-daemon
2020-02-14  8:02 ` [Bug 206517] " bugzilla-daemon

Linux-PM Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-pm/0 linux-pm/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-pm linux-pm/ https://lore.kernel.org/linux-pm \
		linux-pm@vger.kernel.org
	public-inbox-index linux-pm

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-pm


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git