From: Tim Walberg <twalberg@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: 4.8.1 regression with cpufreq governors
Date: Mon, 17 Oct 2016 19:46:06 -0500 [thread overview]
Message-ID: <20161018004606.GA5559@comcast.net> (raw)
May or may not be related to similar reports, but here's what I've just observed
on my system. Built a stock kernel from tags/v4.8.1, relevant cpufreq bits:
CONFIG_ACPI_CPU_FREQ_PSS=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_ATTR_SET=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=m
# CONFIG_X86_PCC_CPUFREQ is not set
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_ACPI_CPUFREQ_CPB=y
Conservative is set as default governer, yet when boot completes, all CPUs are
pegged at the highest frequency. Changing governor to powersave knocks them all
down to the lowest available frequency. Putting them back on conservative (or
ondemand) results in no change in frequency, despite generating load. Switching
to performance of course kicks them back up to high frequency. Basically, the
governors don't seem to be ... governing.
--
twalberg@gmail.com, twalberg@comcast.net
next reply other threads:[~2016-10-18 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 0:46 Tim Walberg [this message]
2016-10-18 21:10 ` 4.8.1 regression with cpufreq governors Rafael J. Wysocki
2016-10-19 14:06 ` Viresh Kumar
2016-10-19 20:06 ` Tim Walberg
2016-10-20 3:29 ` Viresh Kumar
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=20161018004606.GA5559@comcast.net \
--to=twalberg@comcast.net \
--cc=linux-kernel@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.