Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable AMD P-state on Family 17h (threadripper zen 2) #884

Open
CountDizzy opened this issue Feb 2, 2024 · 5 comments
Open

enable AMD P-state on Family 17h (threadripper zen 2) #884

CountDizzy opened this issue Feb 2, 2024 · 5 comments

Comments

@CountDizzy
Copy link

This is a known issue affecting a small portion of zen 2 users.

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

There is a series of patches that could help as well:

https://lore.kernel.org/linux-pm/[email protected]/

The patches are tentatively slated to reach mainline for the 6.9 release.

I have tested the initial patch with TKG, and can confirm that it does enable p-state.

@AdelKS
Copy link
Collaborator

AdelKS commented Feb 2, 2024

I went to the thread and read the entirety of it. Was heartwarming to see it figured out in the end haha.

Basically AMD guy kept saying it's the Mobo guys who are at fault until he took a serious look at it and asked to right people to understand that actually that the Mobo wasn't at fault haha. Needed many people to chim in and report the same error for different Mobo vendors.

@AdelKS
Copy link
Collaborator

AdelKS commented Feb 2, 2024

Does the patch affect every zen2 user or only zen2 thread ripper ?

@ryanmusante
Copy link

Ahh, sounds like 6.9 will be at LTS

@ptr1337
Copy link
Contributor

ptr1337 commented Feb 3, 2024

Does the patch affect every zen2 user or only zen2 thread ripper ?

only thread ripper

@AdelKS
Copy link
Collaborator

AdelKS commented Feb 4, 2024

only thread ripper

So I think you can submit a PR to the community repo for it, then you can add its filename in customization.cfg in the _community_patches variable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants