All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 209069] CPU stuck at 800 MHz at any load
Date: Sun, 06 Sep 2020 18:37:07 +0000	[thread overview]
Message-ID: <bug-209069-137361-R0sIDJRNpQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209069-137361@https.bugzilla.kernel.org/>

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

--- Comment #14 from Doug Smythies (dsmythies@telus.net) ---
Thanks. I re-created your results on my no-hwp processor, by also setting this
in my kernel configuration:

< CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
< # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
---
> # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
> CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=y

The related commits are:

a00ec3874e7d cpufreq: intel_pstate: Select schedutil as the default governor
33aa46f252c7 cpufreq: intel_pstate: Use passive mode by default without HWP

I had thought it would default to the schedutil governor, but didn't.

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

  parent reply	other threads:[~2020-09-06 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 14:51 [Bug 209069] New: CPU stuck at 800 MHz at any load bugzilla-daemon
2020-08-29 15:00 ` [Bug 209069] " bugzilla-daemon
2020-08-29 15:23 ` bugzilla-daemon
2020-08-29 17:25 ` bugzilla-daemon
2020-08-29 18:07 ` bugzilla-daemon
2020-09-02 18:36 ` bugzilla-daemon
2020-09-05 14:33 ` bugzilla-daemon
2020-09-05 16:01 ` bugzilla-daemon
2020-09-06 18:37 ` bugzilla-daemon [this message]
2021-03-21 15:48 ` bugzilla-daemon
2021-04-21  2:16 ` [Bug 209069] CPU stuck at 800 MHz at any load - Xeon E3-1271v3 HSW bugzilla-daemon
2021-04-21  2:16 ` 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-209069-137361-R0sIDJRNpQ@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.