All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218686] Fail to set energy_performance_preference of amd processor on asus ga403uv
Date: Wed, 10 Apr 2024 06:19:00 +0000	[thread overview]
Message-ID: <bug-218686-137361-mlW25j3b27@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218686-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218686

--- Comment #9 from al0uette@outlook.com ---
(In reply to Perry Yuan(AMD) from comment #7)
> (In reply to al0uette from comment #6)
> > (In reply to Perry Yuan(AMD) from comment #5)
> > > Hi,please help to provide this output with below commands.
> > > 
> > > # cd /sys/devices/system/cpu/cpu0/cpufreq
> > > # grep . *
> > > #sudo rdmsr 0xc00102b3 -a
> > > #lscpu -ae
> > > #dmesg
> > 
> > Should I do this with amd_pstate=active commandline?
> 
> Yes, if your kernel is not updated to include the patches which make the
> amd_pstate_epp as the default mode, you would need to add amd_pstate=active
> commandline.
> 
> After you added the amd_pstate=active and boot system up, we can check why 
> the EPP values cannot be changed. 
> 
> Perry.

I've uploaded my output. BTW I do use a quite new kernel (6.9.0-rc1), however
without amd_pstate=active my system uses acpi-cpufreq :(

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2024-04-10  6:19 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06  2:56 [Bug 218686] New: Fail to set energy_performance_preference of amd processor on asus ga403uv bugzilla-daemon
2024-04-08  1:48 ` [Bug 218686] " 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 [this message]
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

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-mlW25j3b27@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.