From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 209069] CPU stuck at 800 MHz at any load
Date: Sat, 05 Sep 2020 14:33:18 +0000 [thread overview]
Message-ID: <bug-209069-137361-AdXsHy1eKH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209069-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209069
Oleh Vinichenko (moonlapse81@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |moonlapse81@gmail.com
--- Comment #9 from Oleh Vinichenko (moonlapse81@gmail.com) ---
I hit this issue as well. On Lenovo ThinkPad W520, with SandyBridge CPU,
Intel(R) Core(TM) i7-2860QM. gradually updated through versions 5.8.* from
older kernels, while keeping kernel configuration the same. If this new change
to be expected as default, there must be documentation about this new behaviour
and what is required to keep active state. What is required to change in kernel
configuration, if needed. This caused massive compilation time regressions and
shoudl not be cast on users without update steps.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-09-05 14:33 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 [this message]
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-AdXsHy1eKH@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).