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] /proc/cpuinfo does not update frequency
Date: Tue, 24 Oct 2017 05:12:32 +0000	[thread overview]
Message-ID: <bug-197009-137361-GwmORPBd9R@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197009-137361@https.bugzilla.kernel.org/>

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

Steven Haigh (netwiz@crc.id.au) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |netwiz@crc.id.au

--- Comment #5 from Steven Haigh (netwiz@crc.id.au) ---
I'm trying to figure out if I've hit a bug or not... My laptop CPU now doesn't
seem to clock down - meaning the temps are higher and the laptop CPU fan is
always running - even when idle.

I noticed it used the intel_pstate driver, I disabled this and tried the
acpi_cpufreq driver, however I see the following:

# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq
2828056
2890338
2889348
2800463

The frequencies supported are:
2901000 2900000 2800000 2700000 2500000 2400000 2300000 2200000 2000000 1900000
1800000 1700000 1600000 1400000 1300000 1200000

I've tried the ondemand and performance gov with no changes.

Is this an actual problem (I think so), or am I checking the freq settings in
the wrong place and the values displayed are making me bark up the wrong tree?

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

  parent reply	other threads:[~2017-10-24  5:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 18:55 [Bug 197009] New: /proc/cpuinfo does not update frequency bugzilla-daemon
2017-09-20 19:03 ` [Bug 197009] " 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 [this message]
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-GwmORPBd9R@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).