From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 177161] New: CPU frequencies in /proc/cpuinfo aren't dynamically updated
Date: Mon, 10 Oct 2016 13:15:42 +0000 [thread overview]
Message-ID: <bug-177161-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=177161
Bug ID: 177161
Summary: CPU frequencies in /proc/cpuinfo aren't dynamically
updated
Product: Power Management
Version: 2.5
Kernel Version: >=4.8
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: itumaykin+kernel@gmail.com
Regression: Yes
Created attachment 241281
--> https://bugzilla.kernel.org/attachment.cgi?id=241281&action=edit
lspci -nn -k -vvv
Hello.
Since 4.8 frequencies in /proc/cpuinfo aren't dynamically updated anymore.
I guess they are stuck to the values written during boot as I get different
values from boot to boot.
This wasn't the case with 4.7.x or any previous kernel series.
Please fix.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2016-10-10 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 13:15 bugzilla-daemon [this message]
2016-10-10 13:15 ` [Bug 177161] CPU frequencies in /proc/cpuinfo aren't dynamically updated bugzilla-daemon
2016-10-10 13:17 ` bugzilla-daemon
2016-10-11 0:02 ` 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-177161-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 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).