linux-pm.vger.kernel.org archive mirror
 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, 21 Mar 2021 15:48:04 +0000	[thread overview]
Message-ID: <bug-209069-137361-cQXOvomi5s@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 #16 from Doug Smythies (dsmythies@telus.net) ---
Hi Rui,

Actually, e-mails about this bug report are on list, because it hasn't been
assigned.

I my opinion, this one can be closed because

CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=y

doesn't have a consistent meaning.
(And I argued this very point with Dirk Brandewie, the original author and
maintainer of the intel_pstate CPU frequency scaling driver, around 2013)

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2021-03-21 15:48 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
2021-03-21 15:48 ` bugzilla-daemon [this message]
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-cQXOvomi5s@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).