All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218171] amd-pstate not loading on zen2 threadripper 3960x (trx40
Date: Tue, 02 Jan 2024 03:23:32 +0000	[thread overview]
Message-ID: <bug-218171-137361-sRGe94r8pO@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 #23 from Perry Yuan(AMD) (Perry.Yuan@amd.com) ---
(In reply to Pedro Nascimento from comment #22)
> Created attachment 305671 [details]
> ACPI dump for Gigabyte TRX40 AORUS PRO WIFI with a 3970X TR
> 
> Here's mine. Note that this is a Gigabyte mobo.
> 
> Machine:
> Type: Desktop System: Gigabyte product: TRX40 AORUS PRO WIFI v: -CF serial:
> N/A
> Mobo: Gigabyte model: TRX40 AORUS PRO WIFI serial: N/A UEFI: American
> Megatrends LLC. v: F6
> date: 09/07/2022
> CPU:
> Info: 32-core model: AMD Ryzen Threadripper 3970X bits: 64 type: MT MCP
> cache: L2: 16 MiB

Hi Pedro, 

The BIOS and some PM firmware are shipped from board vendors, I can see the
pstate driver can work well with our CRB board, but the final BIOS release
comes from vendor, If you would like to get CPPC work on your board, I would
suggest that you request support from board vendor.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2024-01-02  3:23 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
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 [this message]
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-sRGe94r8pO@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.