From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 217589] New: Intel CPU maximum boost frequency reduced after resume from suspend to RAM
Date: Fri, 23 Jun 2023 14:15:02 +0000 [thread overview]
Message-ID: <bug-217589-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217589
Bug ID: 217589
Summary: Intel CPU maximum boost frequency reduced after resume
from suspend to RAM
Product: Power Management
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: bjackson0971@gmail.com
Regression: No
Hardware: MSI MAG Tomahawk Z790 Wifi motherboard, 7D91vH6 BIOS, with Intel
i7-13700K, p-cores overclocked to 5.5GHz, e-cores overclocked to 4.4GHz
Kernel: Linux fedora 6.3.9-200.fc38.x86_64
While running: sysbench cpu run --num-threads=24, then run cat
/sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq | sort -rn
Correct output after reboot:
5500054
5500054
5500000
5500000
5500000
5500000
5500000
5500000
5500000
5500000
5499945
5499945
5499945
5499945
5499945
5499945
4400096
4400044
4400017
4400006
4400004
4400002
4400000
4399960
After suspend to RAM and resume, CPU frequencies are at hardware default
without overclock:
5399941
5399941
5300057
5300057
5300000
5300000
5300000
5300000
5300000
5300000
5300000
5300000
5300000
5300000
4500000
4499951
4200050
4200038
4200036
4200004
4199991
4199985
4199963
4199897
CPU boost clock should retain overclocked speeds after resume from suspend.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-06-23 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:15 bugzilla-daemon [this message]
2023-06-23 14:43 ` [Bug 217589] Intel CPU maximum boost frequency reduced after resume from suspend to RAM bugzilla-daemon
2023-06-23 14:53 ` bugzilla-daemon
2023-06-23 16:29 ` bugzilla-daemon
2023-06-23 16:41 ` bugzilla-daemon
2023-06-23 17:35 ` bugzilla-daemon
2023-06-23 17:58 ` bugzilla-daemon
2023-06-23 17:58 ` bugzilla-daemon
2023-06-26 17:05 ` bugzilla-daemon
2023-06-26 17:32 ` bugzilla-daemon
2023-06-26 18:53 ` bugzilla-daemon
2023-07-18 17:14 ` 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-217589-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).