Linux Power Management development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 222146] 6.18: AMD (Ryzen 5): cannot select existing energy_performance_preference
Date: Sun, 18 Oct 2026 21:25:14 +0000	[thread overview]
Message-ID: <bug-222146-137361-LZU6ExyLqC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222146-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=222146

--- Comment #3 from Steffen Nurpmeso (steffen@sdaoden.eu) ---
merde, of course you can have full lscpu or whatever you want!!
Thanks, indeed.
(I was only sad because of that AMD "territorial pissing" as via
  lid_exists() {
        if [ -z "$LID" ]; then
                # Documentation/firmware-guide/acpi/acpi-lid.rst
                LID=/proc/acpi/button/lid/LID0/state
                [ -f "$LID" ] && return 0
                # amd ryzen 5 220, linux 6.18
                LID=/proc/acpi/button/lid/LID/state
                [ -f "$LID" ] && return 0
                LID=.
        fi
        [ "$LID" != . ]
  }
Cool that really someone deals with bugzilla!!!)


Architecture:                x86_64
  CPU op-mode(s):            32-bit, 64-bit
  Address sizes:             48 bits physical, 48 bits virtual
  Byte Order:                Little Endian
CPU(s):                      12
  On-line CPU(s) list:       0-10:2
  Off-line CPU(s) list:      1-11:2
Vendor ID:                   AuthenticAMD
  Model name:                AMD Ryzen 5 220 w/ Radeon 740M Graphics
    CPU family:              25
    Model:                   124
    Thread(s) per core:      1
    Core(s) per socket:      6
    Socket(s):               1
    Stepping:                0
    Microcode version:       0xa70c00a
    Frequency boost:         enabled
    CPU(s) scaling MHz:      39%
    CPU max MHz:             3201.0000
    CPU min MHz:             406.4770
    BogoMIPS:                6390.28
    Flags:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc rep
                             _good amd_lbr_v2 nopl xtopology nonstop_tsc cpuid
extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2
x2apic movbe popcnt aes xsave avx
                              f16c rdrand lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext
perfctr_core perfctr_nb bpext perfctr_l
                             lc mwaitx cpuid_fault cpb cat_l3 cdp_l3 hw_pstate
ssbd mba perfmon_v2 ibrs ibpb stibp ibrs_enhanced vmmcall fsgsbase bmi1 avx2
smep bmi2 erms invpcid cqm rdt_a av
                             x512f avx512dq rdseed adx smap avx512ifma
clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1
xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm
                             _mbm_local avx512_bf16 clzero irperf xsaveerptr
rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean
flushbyasid decodeassists pausefilter pf
                             threshold vgif x2avic v_spec_ctrl vnmi avx512vbmi
umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg
avx512_vpopcntdq rdpid overflow_recov
                              succor smca fsrm flush_l1d amd_lbr_pmc_freeze
Virtualization features:
  Virtualization:            AMD-V
Caches (sum of all):
  L1d:                       192 KiB (6 instances)
  L1i:                       192 KiB (6 instances)
  L2:                        6 MiB (6 instances)
  L3:                        16 MiB (1 instance)
NUMA:
  NUMA node(s):              1
  NUMA node0 CPU(s):         0-10:2
Vulnerabilities:
  Gather data sampling:      Not affected
  Ghostwrite:                Not affected
  Indirect target selection: Not affected
  Itlb multihit:             Not affected
  L1tf:                      Not affected
  Mds:                       Not affected
  Meltdown:                  Not affected
  Mmio stale data:           Not affected
  Old microcode:             Not affected
  Reg file data sampling:    Not affected
  Retbleed:                  Not affected
  Spec rstack overflow:      Vulnerable
  Spec store bypass:         Mitigation; Speculative Store Bypass disabled via
prctl
  Spectre v1:                Mitigation; usercopy/swapgs barriers and __user
pointer sanitization
  Spectre v2:                Mitigation; Enhanced / Automatic IBRS; IBPB
conditional; STIBP always-on; PBRSB-eIBRS Not affected; BHI Not affected
  Srbds:                     Not affected
  Tsa:                       Mitigation; Clear CPU buffers
  Tsx async abort:           Not affected
  Vmscape:                   Mitigation; IBPB before exit to userspace

-- 
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:[~2026-10-18 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 19:28 [Bug 222146] New: 6.18: AMD (Ryzen 5): cannot select existing energy_performance_preference bugzilla-daemon
2026-10-18 15:45 ` [Bug 222146] " bugzilla-daemon
2026-10-18 21:17 ` bugzilla-daemon
2026-10-18 21:25 ` bugzilla-daemon [this message]
2026-10-19  6:30 ` 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-222146-137361-LZU6ExyLqC@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