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: Thu, 25 Jan 2024 18:41:20 +0000	[thread overview]
Message-ID: <bug-218171-137361-g0xf89NpSD@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 #39 from Pedro Nascimento (pnascimento@gmail.com) ---
Happy to report it is also working on mine.

# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: Gigabyte Technology Co., Ltd.
        Product Name: TRX40 AORUS PRO WIFI
        Version: -CF
        Serial Number: Default string
        UUID: 032e02b4-0499-05fa-cd06-fd0700080009
        Wake-up Type: Power Switch
        SKU Number: Default string
        Family: Default string

Handle 0x0006, DMI type 12, 5 bytes
System Configuration Options
        Option 1: Default string

Handle 0x0007, DMI type 32, 20 bytes
System Boot Information
        Status: No errors detected

analyzing CPU 0:
  driver: amd-pstate-epp
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 550 MHz - 4.55 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 550 MHz and 4.55 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 550 MHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    Boost States: 0
    Total States: 3
    Pstate-P0:  3700MHz
    Pstate-P1:  2800MHz
    Pstate-P2:  2200MHz
=============norminal freq===============================
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
3701
=============norminal perf===============================
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
135
=============highest_perf perf===============================
166
216
211
206
201
196
191
241
241
236
231
166
166
166
166
166
186
181
176
171
166
166
166
166
166
166
166
166
166
166
166
166
166
166
226
221
216
211
206
201
196
191
241
241
166
236
231
166
166
166
166
186
181
176
171
166
166
166
166
166
166
166
226
221
=============lowest_nonlinear_perf perf===============================
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
=============lowest perf===============================
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21
21

-- 
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-25 18:41 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
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 [this message]
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-g0xf89NpSD@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.