From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218171] amd-pstate not loading on zen2 threadripper 3960x (trx40
Date: Wed, 22 Nov 2023 02:43:37 +0000 [thread overview]
Message-ID: <bug-218171-137361-TPeyVpu3Lz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218171-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218171
--- Comment #4 from Perry Yuan(AMD) (Perry.Yuan@amd.com) ---
(In reply to Gino Badouri from comment #3)
> Hi Perry,
>
> I have the following in: Advanced > AMD CBS > NBIO Common Options > SMU
> Common Options
>
> CPPC (Auto / Enabled / Disabled): Enabled
> CPPC Preferred Cores: Enabled
>
> There is no setting to change the default state.
>
> But there seems to be more reports of TRX40 users who are having the same
> problem:
>
> https://forum.level1techs.com/t/is-there-cppc-support-on-threadripper-3000-
> platform/195804/5
>
> https://www.reddit.com/r/threadripper/comments/151l6rn/
> threadripper_amdpstate_driver_on_arch/
>
> https://www.reddit.com/r/linux/comments/15p4bfs/comment/jvvr12s/
> ?utm_source=reddit&utm_medium=web2x&context=3
>
> A while ago I was running a custom Xanmod kernel which had the amd-pstate
> patchset applied before it was sent upstream.
> It was an older revision of the driver of course but it was working for me.
> The only requirement back then was setting the "shared_mem=1" flag on the
> kernel command line.
> But this flag doesn't seem to fix it for me when running linux 6.5.
thanks for your information, could you show me the output of lscpu?
And I would like to see if the mainline kernel work for
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.7-rc2
If mainline 6.7 still have problem on your system, I would guess there are some
missing thing we need to figure out.
Perry.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-11-22 2:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 9:51 [Bug 218171] New: amd-pstate not loading on zen2 threadripper 3960x (trx40 bugzilla-daemon
2023-11-21 9:56 ` [Bug 218171] " bugzilla-daemon
2023-11-21 10:16 ` bugzilla-daemon
2023-11-21 10:48 ` bugzilla-daemon
2023-11-22 2:43 ` bugzilla-daemon [this message]
2023-11-22 8:34 ` bugzilla-daemon
2023-11-22 8:45 ` bugzilla-daemon
2023-11-22 8:49 ` bugzilla-daemon
2023-11-22 8:56 ` bugzilla-daemon
2023-11-22 9:01 ` bugzilla-daemon
2023-11-22 9:04 ` bugzilla-daemon
2023-11-22 9:25 ` bugzilla-daemon
2023-11-23 7:57 ` bugzilla-daemon
2023-12-01 12:28 ` bugzilla-daemon
2023-12-04 5:31 ` bugzilla-daemon
2023-12-04 5:55 ` bugzilla-daemon
2023-12-04 8:30 ` bugzilla-daemon
2023-12-04 8:45 ` bugzilla-daemon
2023-12-04 9:43 ` bugzilla-daemon
2023-12-07 5:52 ` bugzilla-daemon
2023-12-15 11:25 ` bugzilla-daemon
2023-12-15 11:46 ` bugzilla-daemon
2023-12-30 3:28 ` bugzilla-daemon
2024-01-02 3:23 ` bugzilla-daemon
2024-01-02 10:10 ` bugzilla-daemon
2024-01-16 22:27 ` bugzilla-daemon
2024-01-16 22:33 ` bugzilla-daemon
2024-01-17 3:12 ` bugzilla-daemon
2024-01-17 16:24 ` bugzilla-daemon
2024-01-17 21:42 ` bugzilla-daemon
2024-01-17 21:49 ` bugzilla-daemon
2024-01-18 6:30 ` bugzilla-daemon
2024-01-18 22:46 ` bugzilla-daemon
2024-01-22 22:08 ` bugzilla-daemon
2024-01-22 22:09 ` bugzilla-daemon
2024-01-22 22:10 ` bugzilla-daemon
2024-01-25 6:17 ` bugzilla-daemon
2024-01-25 9:21 ` bugzilla-daemon
2024-01-25 12:25 ` bugzilla-daemon
2024-01-25 14:39 ` bugzilla-daemon
2024-01-25 18:41 ` bugzilla-daemon
2024-01-26 4:33 ` bugzilla-daemon
2024-01-26 16:36 ` bugzilla-daemon
2024-02-01 19:34 ` bugzilla-daemon
2024-02-02 14:28 ` bugzilla-daemon
2024-02-04 14:08 ` bugzilla-daemon
2024-03-10 15:33 ` bugzilla-daemon
2024-03-22 7:38 ` bugzilla-daemon
2024-03-25 2:28 ` 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-218171-137361-TPeyVpu3Lz@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.