From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218705] amd_pstate fails to load on AMD 5950x with Asus ROG CROSSHAIR VIII DARK HERO x570
Date: Fri, 26 Apr 2024 17:40:58 +0000 [thread overview]
Message-ID: <bug-218705-137361-K3HmCJxUjj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218705-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218705
--- Comment #21 from Andrei Amuraritei (andamu@posteo.net) ---
Not sure if relevant, but I found out that Fedora also has amd-pstate-ut
module, and loading this, i see the following in dmesg:
boot kernel with amd_pstate=passive
[Fr Apr 26 19:37:29 2024] amd_pstate_ut: 1 amd_pstate_ut_acpi_cpc_valid
success!
[Fr Apr 26 19:37:29 2024] amd_pstate_ut: 2 amd_pstate_ut_check_enabled
success!
[Fr Apr 26 19:37:29 2024] amd_pstate_ut: amd_pstate_ut_check_perf cpu0
highest=221 166 nominal=111 111 lowest_nonlinear=57 57 lowest=19 19, they
should be equal!
[Fr Apr 26 19:37:29 2024] amd_pstate_ut: 3 amd_pstate_ut_check_perf fail!
[Fr Apr 26 19:37:29 2024] amd_pstate_ut: 4 amd_pstate_ut_check_freq
success!
boot kernel with amd_pstate=active
[Fr Apr 26 19:35:07 2024] amd_pstate_ut: 1 amd_pstate_ut_acpi_cpc_valid
success!
[Fr Apr 26 19:35:07 2024] amd_pstate_ut: 2 amd_pstate_ut_check_enabled
success!
[Fr Apr 26 19:35:07 2024] amd_pstate_ut: amd_pstate_ut_check_perf cpu0
highest=221 166 nominal=111 111 lowest_nonlinear=57 57 lowest=19 19, they
should be equal!
[Fr Apr 26 19:35:07 2024] amd_pstate_ut: 3 amd_pstate_ut_check_perf fail!
[Fr Apr 26 19:35:07 2024] amd_pstate_ut: 4 amd_pstate_ut_check_freq
success!
--
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:[~2024-04-26 17:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 16:52 [Bug 218705] New: amd_pstate fails to load on AMD 5950x with Asus ROG CROSSHAIR VIII DARK HERO x570 bugzilla-daemon
2024-04-10 16:54 ` [Bug 218705] " 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 [this message]
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-K3HmCJxUjj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).