From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 217630] Kernel fails to load amd_pstate driver on 3970x while Windows works well on the same machine
Date: Tue, 04 Jul 2023 02:14:52 +0000 [thread overview]
Message-ID: <bug-217630-137361-1uYpAevv0T@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217630-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217630
Bagas Sanjaya (bagasdotme@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bagasdotme@gmail.com
--- Comment #2 from Bagas Sanjaya (bagasdotme@gmail.com) ---
(In reply to Pavel S from comment #0)
> I have 3970x CPU installed into Gigabyte Designare TRX40 rev 1.0
> motherboard. The UEFI is updated to version F6 so AGESA has version 1.0.0.7.
>
> CPPC is explicitly enabled in UEFI settings. It definitely works in Windows:
>
> > Information 7/3/2023 4:46:04 PM
> > Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor
> 63
> > in group 0 exposes the following power management capabilities:
> > Idle state type: ACPI Idle (C) States (2 state(s))
> > Performance state type: ACPI Collaborative Processor Performance Control
>
> Kernel 6.3 fails to load amd_pstate with both "amd_pstate=active" and
> "amd_pstate=passive" kernel parameters with the following message:
>
> > amd_pstate: the _CPC object is not present in SBIOS or ACPI disabled
>
> Kernel 6.4.0 doesn't shows the same error "amd_pstate=active",
> "amd_pstate=passive" and "amd_pstate=guided".
>
Do you mean this issue doesn't show up anymore in v6.4.y?
--
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-07-04 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 17:38 [Bug 217630] New: Kernel fails to load amd_pstate driver on 3970x while Windows works well on the same machine bugzilla-daemon
2023-07-03 23:19 ` [Bug 217630] " bugzilla-daemon
2023-07-04 2:14 ` bugzilla-daemon [this message]
2023-07-04 16:56 ` bugzilla-daemon
2023-08-01 6:03 ` 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-217630-137361-1uYpAevv0T@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.