All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 206517] New: scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX
Date: Thu, 13 Feb 2020 15:27:52 +0000	[thread overview]
Message-ID: <bug-206517-137361@https.bugzilla.kernel.org/> (raw)

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.

             reply	other threads:[~2020-02-13 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 15:27 bugzilla-daemon [this message]
2020-02-14  8:02 ` [Bug 206517] scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX bugzilla-daemon
2020-06-29 12:16 ` bugzilla-daemon
2020-06-29 12:17 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-206517-137361@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.