From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 209069] CPU stuck at 800 MHz at any load
Date: Wed, 02 Sep 2020 18:36:11 +0000 [thread overview]
Message-ID: <bug-209069-137361-eHpC01T6l9@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 #8 from Doug Smythies (dsmythies@telus.net) ---
My best guess is that with kernel 5.4.48 you were running with the intel_pstate
CPU frequency scaling driver in active mode, and that you are now running in
passive mode. As of kernel 5.8-rc1 by default processors without HWP will
default to passive mode. If you still have kernel 5.4.48, you could check.
Your Skylake system has HWP, and wouldn't default to passive mode.
However, you also mentioned Sandy Bridge and Westmere systems being unaffected.
Sandy Bridge doesn't have HWP, and Westmere might even pre-date the pstate
driver, I don't know. Anyway, this seems inconsistent with my "best guess"
above. Suggest you check them, with those same instructions from comment 1.
If you think, or conclude, that you used to run in active mode you can either
force active mode or force the schedutil governor in passive mode via the grub
command line to get out of your locked low frequency state.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-09-02 18:36 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 [this message]
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
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-eHpC01T6l9@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.