From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 220013] [REGRESSION, BISECTED] acpi-cpufreq: Boost disablement not being restored after resume from suspend
Date: Thu, 17 Apr 2025 05:00:43 +0000 [thread overview]
Message-ID: <bug-220013-137361-oFqLEKqrUY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220013-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220013
--- Comment #5 from Nicholas Chin (nic.c3.14@gmail.com) ---
I did some more testing and debugging and it seems like when cpufreq_online()
runs after waking the system, policy->boost_enabled and cpufreq_boost_enabled()
are both 0, so the set_boost() at the end of that function is never run.
cpufreq_boost_enabled() being 0 indicates that the MSR has boosting disabled,
but when I read out that MSR using rdmsr the bit seems to indicate that it is
actually enabled (I am aware of the inverted logic of that bit). set_boost()
seems to be the only place in the kernel that causes that MSR to be modified,
and I didn't see any extra calls to it in my debug logs, so it seems like
something else (outside the kernel?) is setting that MSR.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2025-04-17 5:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 4:36 [Bug 220013] New: [REGRESSION, BISECTED] acpi-cpufreq: Boost disablement not being restored after resume from suspend bugzilla-daemon
2025-04-15 4:39 ` [Bug 220013] " bugzilla-daemon
2025-04-15 8:42 ` bugzilla-daemon
2025-04-15 10:27 ` bugzilla-daemon
2025-04-16 4:53 ` bugzilla-daemon
2025-04-16 5:35 ` bugzilla-daemon
2025-04-17 5:00 ` bugzilla-daemon [this message]
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-220013-137361-oFqLEKqrUY@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).