linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@kernel.org
Subject: [Bug 197009] New: /proc/cpuinfo does not update frequency
Date: Wed, 20 Sep 2017 18:55:27 +0000	[thread overview]
Message-ID: <bug-197009-137361@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 197009
           Summary: /proc/cpuinfo does not update frequency
           Product: Power Management
           Version: 2.5
    Kernel Version: 4.13
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: aleksey@rybalkin.org
        Regression: No

Created attachment 258537
  --> https://bugzilla.kernel.org/attachment.cgi?id=258537&action=edit
kernel config

The 4.13 kernel with intel_pstate=passive (or active) does not appear to
correctly update the CPU frequency in /proc/cpuinfo

After booting the reported frequency (but not the real frequency) is stuck on
one value and does not update:

$ grep MHz /proc/cpuinfo
cpu MHz         : 2194.859
cpu MHz         : 2194.859
cpu MHz         : 2194.859
cpu MHz         : 2194.859

hardware: ThinkPad X250
cpu: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
kernel: 4.13.3 vanilla (config attached)

As far as I remember this worked in 4.11 and broke after 4.12, I can double
check if needed.

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

             reply	other threads:[~2017-09-20 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 18:55 bugzilla-daemon [this message]
2017-09-20 19:03 ` [Bug 197009] /proc/cpuinfo does not update frequency bugzilla-daemon
2017-09-20 19:14 ` bugzilla-daemon
2017-09-22  5:01 ` bugzilla-daemon
2017-10-11  5:51 ` bugzilla-daemon
2017-10-17  1:41 ` bugzilla-daemon
2017-10-24  5:12 ` bugzilla-daemon
2017-11-02  1:44 ` bugzilla-daemon
2017-11-05 22:28 ` bugzilla-daemon
2017-11-18 15:34 ` bugzilla-daemon
2017-11-20  5:28 ` bugzilla-daemon
2017-11-20 14:36 ` bugzilla-daemon
2017-11-20 19:12 ` bugzilla-daemon
2017-11-20 22:16 ` bugzilla-daemon
2017-11-20 22:22 ` bugzilla-daemon
2017-11-21  1:30 ` 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-197009-137361@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-pm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).