From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218805] New: CPU stuck to low frequency after resume from sleep
Date: Fri, 03 May 2024 19:31:22 +0000 [thread overview]
Message-ID: <bug-218805-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218805
Bug ID: 218805
Summary: CPU stuck to low frequency after resume from sleep
Product: Power Management
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: bogdan.nicolae@gmail.com
Regression: No
Kernel version: 6.8.7 #1 SMP PREEMPT_DYNAMIC
Problem: On initial boot, everything works fine. After suspend-resume,
intel_cpufreq policy is stuck well below hardware limits (1.32 Ghz instead of
3.30 Ghz), as seen below. Manually trying to raise the upper limit is not
possible.
analyzing CPU 5:
driver: intel_cpufreq
CPUs which run at the same hardware frequency: 5
CPUs which need to have their frequency coordinated by software: 5
maximum transition latency: 20.0 us
hardware limits: 1.20 GHz - 3.30 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.20 GHz and 1.32 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.10 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
25500 MHz max turbo 4 active cores
25500 MHz max turbo 3 active cores
25500 MHz max turbo 2 active cores
25500 MHz max turbo 1 active cores
--
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:[~2024-05-03 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 19:31 bugzilla-daemon [this message]
2024-05-04 9:04 ` [Bug 218805] CPU stuck to low frequency after resume from sleep bugzilla-daemon
2024-05-04 13:26 ` bugzilla-daemon
2024-05-05 8:48 ` 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-218805-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 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.