From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218171] amd-pstate not loading on zen2 threadripper 3960x (trx40
Date: Wed, 22 Nov 2023 08:34:08 +0000 [thread overview]
Message-ID: <bug-218171-137361-w9tdKWuvSc@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 #5 from Gino Badouri (badouri.g@gmail.com) ---
Hi Perry,
Thanks for looking into this.
I've updated to 6.7 rc2.
# uname -a
Linux pve 6.7.0-060700rc2-generic #202311192332 SMP PREEMPT_DYNAMIC Sun Nov 19
23:40:20 UTC 2023 x86_64 GNU/Linux
# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.7.0-060700rc2-generic root=/dev/mapper/pve-root ro
quiet iommu=pt amd_iommu=on kvm_amd.npt=1 kvm_amd.avic=1 nmi_watchdog=0
video=vesafb:off video=efifb:off video=simplefb:off nomodeset
initcall_blacklist=sysfb_init modprobe.blacklist=nouveau
modprobe.blacklist=amdgpu modprobe.blacklist=radeon modprobe.blacklist=nvidia
hugepagesz=1G default_hugepagesz=2M amd_pstate=active
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 43 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 48
On-line CPU(s) list: 0-47
Vendor ID: AuthenticAMD
BIOS Vendor ID: Advanced Micro Devices, Inc.
Model name: AMD Ryzen Threadripper 3960X 24-Core Processor
BIOS Model name: AMD Ryzen Threadripper 3960X 24-Core Processor
Unknown
CPU @ 3.8GHz
BIOS CPU family: 107
CPU family: 23
Model: 49
Thread(s) per core: 2
Core(s) per socket: 24
Socket(s): 1
Stepping: 0
Frequency boost: enabled
CPU(s) scaling MHz: 58%
CPU max MHz: 3800.0000
CPU min MHz: 2200.0000
BogoMIPS: 7585.72
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mc
a cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall
n
x mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc
rep_go
od nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl
p
ni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2
movbe
popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
sv
m extapic cr8_legacy abm sse4a misalignsse
3dnowprefetc
h osvw ibs skinit wdt tce topoext perfctr_core
perfctr_
nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3
hw_pstate
ssbd mba ibpb stibp vmmcall fsgsbase bmi1 avx2 smep
bm
i2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni
xsa
veopt xsavec xgetbv1 cqm_llc cqm_occup_llc
cqm_mbm_tota
l cqm_mbm_local clzero irperf xsaveerptr rdpru
wbnoinvd
amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale
vm
cb_clean flushbyasid decodeassists pausefilter
pfthresh
old avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid
ov
erflow_recov succor smca sev sev_es
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 768 KiB (24 instances)
L1i: 768 KiB (24 instances)
L2: 12 MiB (24 instances)
L3: 128 MiB (8 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-47
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Retbleed: Mitigation; untrained return thunk; SMT enabled with
ST
IBP protection
Spec rstack overflow: Mitigation; Safe RET
Spec store bypass: Mitigation; Speculative Store Bypass disabled via
prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user
pointer
sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, STIBP
always-
on, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
Unfortunately the driver is still printing:
[ 0.640246] amd_pstate: the _CPC object is not present in SBIOS or ACPI
disabled
If it helps, I've uploaded the acpi tables in both dat and dsl format here:
https://mega.nz/file/apkElTBL#JEmN0vmBSh7d-hbDiN-V0lwG7mwZQfitqnv4iVk0ACU
--
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-11-22 8:34 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 [this message]
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
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-w9tdKWuvSc@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).