From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215801] New: Rmmod'ing amd-pstate doesn't restore acpi-cpufreq
Date: Tue, 05 Apr 2022 01:43:08 +0000 [thread overview]
Message-ID: <bug-215801-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215801
Bug ID: 215801
Summary: Rmmod'ing amd-pstate doesn't restore acpi-cpufreq
Product: Power Management
Version: 2.5
Kernel Version: 5.17.1
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: aros@gmx.com
Regression: No
It's nice that you can now replace acpi-cpufreq with amd-pstate using replace=1
but what about the opposite?
Can it be done without rebooting if acpi-cpufreq is built-in?
Would be really nice to have.
Meanwhile some sort of power managerment still works after `rmmod amd-pstate`
because I see that reported frequencies in /proc/cpuinfo change: one or two
random cores are oscillating between 1700 and 2000MHz, all the others are stuck
at 3800MHz.
--
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:[~2022-04-05 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 1:43 bugzilla-daemon [this message]
2022-04-11 16:22 ` [Bug 215801] Rmmod'ing amd-pstate doesn't restore acpi-cpufreq bugzilla-daemon
2023-09-20 10:54 ` bugzilla-daemon
2023-09-21 5:40 ` bugzilla-daemon
2023-09-21 8:18 ` bugzilla-daemon
2023-09-27 13:01 ` bugzilla-daemon
2023-09-28 2:31 ` 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-215801-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).