From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218685] asus-nb-wmi fails to load due to conflict with amd-pmf
Date: Wed, 10 Apr 2024 05:29:10 +0000 [thread overview]
Message-ID: <bug-218685-215701-iQoGJNBeb5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218685-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218685
--- Comment #16 from al0uette@outlook.com ---
[root@Zephyrus:~]# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
performance
performance
performance
performance
performance
performance
performance
performance
performance
performance
performance
performance
performance
performance
performance
performance
[root@Zephyrus:~]# cat /sys/kernel/debug/amd_pmf/current_power_limits
spl:45000 fppt:65000 sppt:65000 sppt_apu_only:54000 stt_min:0 stt[APU]:0
stt[HS2]: 0
[root@Zephyrus:~]# echo "powersave" | tee
/sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave
[root@Zephyrus:~]# cat /sys/kernel/debug/amd_pmf/current_power_limits
spl:45000 fppt:65000 sppt:65000 sppt_apu_only:54000 stt_min:0 stt[APU]:0
stt[HS2]: 0
Seems that they don't change
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-04-10 5:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-218685-215701@https.bugzilla.kernel.org/>
2024-04-09 15:49 ` [Bug 218685] asus-nb-wmi fails to load due to conflict with amd-pmf bugzilla-daemon
2024-04-09 15:51 ` bugzilla-daemon
2024-04-09 15:57 ` bugzilla-daemon
2024-04-09 16:30 ` bugzilla-daemon
2024-04-10 1:15 ` bugzilla-daemon
2024-04-10 4:49 ` bugzilla-daemon
2024-04-10 5:03 ` bugzilla-daemon
2024-04-10 5:19 ` bugzilla-daemon
2024-04-10 5:29 ` bugzilla-daemon [this message]
2024-04-10 5:35 ` bugzilla-daemon
2024-04-10 5:35 ` bugzilla-daemon
2024-04-10 5:45 ` bugzilla-daemon
2024-04-10 6:05 ` bugzilla-daemon
2024-04-10 6:09 ` bugzilla-daemon
2024-04-10 6:10 ` bugzilla-daemon
2024-04-10 11:22 ` bugzilla-daemon
2024-04-10 11:24 ` bugzilla-daemon
2024-04-10 11:29 ` bugzilla-daemon
2024-04-10 11:30 ` bugzilla-daemon
2024-04-10 11:31 ` bugzilla-daemon
2024-04-10 11:35 ` bugzilla-daemon
2024-04-10 11:49 ` bugzilla-daemon
2024-04-10 11:52 ` bugzilla-daemon
2024-04-10 11:58 ` bugzilla-daemon
2024-04-10 12:28 ` bugzilla-daemon
2024-04-10 12:44 ` bugzilla-daemon
2024-04-10 14:24 ` bugzilla-daemon
2024-04-10 14:38 ` bugzilla-daemon
2024-04-10 14:45 ` bugzilla-daemon
2024-04-10 14:54 ` bugzilla-daemon
2024-04-10 15:22 ` bugzilla-daemon
2024-04-12 7:08 ` bugzilla-daemon
2024-04-12 11:21 ` bugzilla-daemon
2024-04-12 13:04 ` bugzilla-daemon
2024-04-12 13:32 ` 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-218685-215701-iQoGJNBeb5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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.