From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218705] New: amd_pstate fails to load on AMD 5950x with Asus ROG CROSSHAIR VIII DARK HERO x570
Date: Wed, 10 Apr 2024 16:52:17 +0000 [thread overview]
Message-ID: <bug-218705-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218705
Bug ID: 218705
Summary: amd_pstate fails to load on AMD 5950x with Asus ROG
CROSSHAIR VIII DARK HERO x570
Product: Power Management
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: andamu@posteo.net
Regression: No
Hi!
Sorry if the formatting is broken or this is unreadable. Description preview is
broken it seems.
amd_pstate fails to load on this hardware:
CPU: AMD 5950x
Mainboard: Asus ROG CROSSHAIR VIII DARK HERO x570 running UEFI version 4702
OS: Fedora 39 Wayland with kernel Linux 6.8.4-200.fc39.x86_64
amd_pstate does not get automatically enabled. dmesg -T | grep pstate says:
[Tue Apr 9 17:24:36 2024] amd_pstate: driver load is disabled, boot with
specific mode to enable this
No cppc found in output from lscpu. In UEFI the following are activated:
Advanced > AMD CBS > NBIO Common Options > SMU Common Options
CPPC (Auto / Enabled / Disabled): Enabled
CPPC Preferred Cores: Enabled
--
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-10 16:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 16:52 bugzilla-daemon [this message]
2024-04-10 16:54 ` [Bug 218705] amd_pstate fails to load on AMD 5950x with Asus ROG CROSSHAIR VIII DARK HERO x570 bugzilla-daemon
2024-04-15 16:04 ` bugzilla-daemon
2024-04-22 8:04 ` bugzilla-daemon
2024-04-22 8:06 ` bugzilla-daemon
2024-04-22 11:07 ` bugzilla-daemon
2024-04-25 3:36 ` bugzilla-daemon
2024-04-25 3:36 ` bugzilla-daemon
2024-04-25 5:27 ` bugzilla-daemon
2024-04-25 15:25 ` bugzilla-daemon
2024-04-25 15:26 ` bugzilla-daemon
2024-04-25 15:26 ` bugzilla-daemon
2024-04-25 15:27 ` bugzilla-daemon
2024-04-25 15:27 ` bugzilla-daemon
2024-04-25 15:27 ` bugzilla-daemon
2024-04-25 15:33 ` bugzilla-daemon
2024-04-25 17:51 ` bugzilla-daemon
2024-04-26 17:24 ` bugzilla-daemon
2024-04-26 17:25 ` bugzilla-daemon
2024-04-26 17:25 ` bugzilla-daemon
2024-04-26 17:27 ` bugzilla-daemon
2024-04-26 17:40 ` bugzilla-daemon
2024-04-27 0:49 ` bugzilla-daemon
2024-04-27 6:38 ` bugzilla-daemon
2024-04-27 13:25 ` bugzilla-daemon
2024-04-27 22:58 ` bugzilla-daemon
2024-04-30 6:48 ` bugzilla-daemon
2024-05-07 8:40 ` bugzilla-daemon
2024-05-13 19:04 ` bugzilla-daemon
2024-05-14 2:30 ` bugzilla-daemon
2024-05-14 18:25 ` bugzilla-daemon
2024-05-15 13:44 ` bugzilla-daemon
2024-05-21 7:19 ` 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-218705-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 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.