From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218686] New: Fail to set energy_performance_preference of amd processor on asus ga403uv
Date: Sat, 06 Apr 2024 02:56:57 +0000 [thread overview]
Message-ID: <bug-218686-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218686
Bug ID: 218686
Summary: Fail to set energy_performance_preference of amd
processor on asus ga403uv
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: al0uette@outlook.com
Regression: No
Created attachment 306091
--> https://bugzilla.kernel.org/attachment.cgi?id=306091&action=edit
ssdt table containing _CPC things
I enabled amd-pstate-epp driver by appending 'amd_pstate=active' to kernel
cmdline, and set scaling_governer to powersave, and
'cat
/sys/devices/system/cpu/cpu*/cpufreq/energy_performance_available_preferences'
do show
'default performance balance_performance balance_power power'.
However when I try to change epp to anything other than 'performance'(which is
the default) with something like
'echo power |sudo tee
/sys/devices/system/cpu/cpufreq/policy*/energy_performance_preference',
I get 'tee:
/sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference: Unknown
error 524', which, according to source code, I guess is ENOTSUPP. And I guess
it's because cppc_set_epp_perf() in linux/drivers/acpi/cppc_acpi.c checks
CPC_IN_PCC(epp_set_reg), and think the register doesn't exist. However I do see
the _CPC things in my ssdt. Don't know its' a bug in kernel or BIOS so I report
it here
--
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-04-06 2:56 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 2:56 bugzilla-daemon [this message]
2024-04-08 1:48 ` [Bug 218686] Fail to set energy_performance_preference of amd processor on asus ga403uv bugzilla-daemon
2024-04-10 3:36 ` bugzilla-daemon
2024-04-10 5:28 ` bugzilla-daemon
2024-04-10 5:33 ` bugzilla-daemon
2024-04-10 5:39 ` bugzilla-daemon
2024-04-10 5:41 ` bugzilla-daemon
2024-04-10 5:46 ` bugzilla-daemon
2024-04-10 5:48 ` bugzilla-daemon
2024-04-10 6:17 ` bugzilla-daemon
2024-04-10 6:19 ` bugzilla-daemon
2024-04-10 6:26 ` bugzilla-daemon
2024-04-10 6:27 ` bugzilla-daemon
2024-04-10 6:29 ` bugzilla-daemon
2024-04-10 6:42 ` bugzilla-daemon
2024-04-10 6:43 ` bugzilla-daemon
2024-04-10 6:47 ` bugzilla-daemon
2024-04-10 6:49 ` bugzilla-daemon
2024-04-10 6:51 ` bugzilla-daemon
2024-04-10 6:55 ` bugzilla-daemon
2024-04-10 7:02 ` bugzilla-daemon
2024-04-10 7:12 ` bugzilla-daemon
2024-04-10 7:21 ` bugzilla-daemon
2024-04-10 7:26 ` bugzilla-daemon
2024-04-10 7:27 ` bugzilla-daemon
2024-04-10 16:08 ` bugzilla-daemon
2024-04-10 16:08 ` bugzilla-daemon
2024-04-11 4:18 ` bugzilla-daemon
2024-04-11 4:19 ` bugzilla-daemon
2024-04-11 4:20 ` bugzilla-daemon
2024-04-11 5:29 ` bugzilla-daemon
2024-04-11 5:30 ` bugzilla-daemon
2024-04-11 7:25 ` bugzilla-daemon
2024-04-11 9:02 ` bugzilla-daemon
2024-04-11 9:15 ` bugzilla-daemon
2024-04-11 10:09 ` bugzilla-daemon
2024-04-11 11:14 ` bugzilla-daemon
2024-04-11 12:56 ` bugzilla-daemon
2024-04-11 15:53 ` bugzilla-daemon
2024-04-11 15:54 ` bugzilla-daemon
2024-04-15 8:37 ` bugzilla-daemon
2024-04-18 7:36 ` bugzilla-daemon
2024-04-18 7:56 ` bugzilla-daemon
2024-04-18 8:41 ` bugzilla-daemon
2024-04-23 7:03 ` bugzilla-daemon
2024-04-23 7:25 ` bugzilla-daemon
2024-05-17 8:50 ` bugzilla-daemon
2024-05-17 11:53 ` bugzilla-daemon
2024-05-17 15:11 ` 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-218686-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 read-only IMAP folder(s) and NNTP newsgroup(s).