Bug 213023 - Could not resolve symbol [\_PR.CPU0._CPC]
Summary: Could not resolve symbol [\_PR.CPU0._CPC]
Status: REOPENED
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: All Linux
: P1 high
Assignee: acpi_bios
URL:
Keywords:
: 215830 216070 216169 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-05-10 17:23 UTC by sander44
Modified: 2022-11-11 15:32 UTC (History)
30 users (show)

See Also:
Kernel Version: 5.12.2
Tree: Mainline
Regression: No


Attachments
ACPIDUMP + DMESG outputs for linux and linux-lts (416.77 KB, application/zip)
2021-05-21 00:32 UTC, Paulo Marcos de Souza Arruda do Nascimento
Details
acpidump-5.10.35-1.zip - acpidump (282.73 KB, application/x-zip-compressed)
2021-05-21 17:34 UTC, sander44
Details
MSI MPG Z390 Gaming Pro Carbon acpidump (1.53 MB, text/plain)
2021-06-03 12:07 UTC, Juhász Péter Károly
Details
[PATCH] ACPI: Use _OSC query results to determine caps rather then the commit results (2.46 KB, patch)
2021-06-07 10:06 UTC, Hans de Goede
Details | Diff
[PATCH] ACPI: Only run _OSC without the query flag on machines with native USB4 support (3.65 KB, patch)
2021-06-08 09:47 UTC, Hans de Goede
Details | Diff
[PATCH] ACPI: Pass the same capabilities to the _OSC regardless of the query flag (3.82 KB, patch)
2021-06-08 17:15 UTC, Hans de Goede
Details | Diff
T440s dmesg (5.03 KB, text/plain)
2022-03-13 08:38 UTC, John Humes
Details
acpidump + dmesg - 5.17.4 (190.53 KB, application/zip)
2022-04-27 09:36 UTC, Lethe
Details
acpidump, ASRock B460M-ITX/ac (P1.60 BIOS) motherboard + Intel Core i7-10700K CPU (1.33 MB, text/plain)
2022-06-28 15:55 UTC, CUI Hao
Details
patch with potential fix + more debugging messages (3.25 KB, patch)
2022-06-30 15:18 UTC, Mario Limonciello (AMD)
Details | Diff
My acpidump & kernel messages (ASRock B460M-ITX/ac (P1.60 BIOS) motherboard + Intel Core i7-10700K CPU) (326.64 KB, application/gzip)
2022-06-30 17:32 UTC, CUI Hao
Details
patch with potential fix: Only let cppc_acpi run if CPPCv2 was not masked (3.22 KB, patch)
2022-06-30 18:04 UTC, Mario Limonciello (AMD)
Details | Diff

Description sander44 2021-05-10 17:23:25 UTC
Hi Kernel Team,

Observe this issue:

[    2.057284] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330)
[    2.057339] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529)
[    2.057443] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330)
[    2.057484] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529)
[    2.057569] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330)
[    2.057610] ACPI Error: Aborting method \_PR.CPU3._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529)


lscpu
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          4
On-line CPU(s) list:             0-3
Thread(s) per core:              2
Core(s) per socket:              2
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           142
Model name:                      Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz
Stepping:                        9
CPU MHz:                         2200.000
CPU max MHz:                     3400.0000
CPU min MHz:                     400.0000
BogoMIPS:                        4399.99
Virtualization:                  VT-x
L1d cache:                       64 KiB
L1i cache:                       64 KiB
L2 cache:                        512 KiB
L3 cache:                        4 MiB
NUMA node0 CPU(s):               0-3
Vulnerability Itlb multihit:     KVM: Mitigation: VMX disabled
Vulnerability L1tf:              Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
Vulnerability Mds:               Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds:             Mitigation; Microcode
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_t
                                 sc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm
                                  pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibp
                                 b stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsav
                                 ec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d

 dmesg | grep -E "ACPI|BIOS"
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006cdbefff] usable
[    0.000000] BIOS-e820: [mem 0x000000006cdbf000-0x000000006cdbffff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000006cdc0000-0x000000006cdc0fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000006cdc1000-0x000000007a465fff] usable
[    0.000000] BIOS-e820: [mem 0x000000007a466000-0x000000007a7a4fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007a7a5000-0x000000007a7e2fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000007a7e3000-0x000000007afbafff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000007afbb000-0x000000007b3fdfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007b3fe000-0x000000007b3fefff] usable
[    0.000000] BIOS-e820: [mem 0x000000007b3ff000-0x000000007fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000047effffff] usable
[    0.000000] reserve setup_data: [mem 0x000000006cdbf000-0x000000006cdbffff] ACPI NVS
[    0.000000] reserve setup_data: [mem 0x000000007a7a5000-0x000000007a7e2fff] ACPI data
[    0.000000] reserve setup_data: [mem 0x000000007a7e3000-0x000000007afbafff] ACPI NVS
[    0.000000] efi: ACPI 2.0=0x7a7b1000 ACPI=0x7a7b1000 SMBIOS=0x7b30b000 SMBIOS 3.0=0x7b30a000 ESRT=0x7b30c858 MOKvar=0x786d6000
[    0.000000] SMBIOS 3.0.0 present.
[    0.000000] DMI: Intel Corporation NUC7i5BNH/NUC7i5BNB, BIOS BNKBL357.86A.0050.2017.0816.2002 08/16/2017
[    0.013016] ACPI: Early table checksum verification disabled
[    0.013019] ACPI: RSDP 0x000000007A7B1000 000024 (v02 INTEL )
[    0.013024] ACPI: XSDT 0x000000007A7B10A8 0000D4 (v01 INTEL  NUC7i5BN 00000032 AMI  00010013)
[    0.013030] ACPI: FACP 0x000000007A7DA100 000114 (v06 INTEL  NUC7i5BN 00000032 AMI  00010013)
[    0.013037] ACPI: DSDT 0x000000007A7B1210 028EEC (v02 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013041] ACPI: FACS 0x000000007AFBAC40 000040
[    0.013044] ACPI: APIC 0x000000007A7DA218 000084 (v03 INTEL  NUC7i5BN 00000032 AMI  00010013)
[    0.013048] ACPI: FPDT 0x000000007A7DA2A0 000044 (v01 INTEL  NUC7i5BN 00000032 AMI  00010013)
[    0.013051] ACPI: MCFG 0x000000007A7DA2E8 00003C (v01 INTEL  NUC7i5BN 00000032 MSFT 00000097)
[    0.013055] ACPI: SSDT 0x000000007A7DA328 000359 (v01 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013058] ACPI: FIDT 0x000000007A7DA688 00009C (v01 INTEL  NUC7i5BN 00000032 AMI  00010013)
[    0.013062] ACPI: SSDT 0x000000007A7DA728 003174 (v02 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013065] ACPI: HPET 0x000000007A7DD8A0 000038 (v01 INTEL  NUC7i5BN 00000032 MSFT 0000005F)
[    0.013069] ACPI: SSDT 0x000000007A7DD8D8 0009B2 (v02 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013072] ACPI: UEFI 0x000000007A7DE290 000042 (v01 INTEL  NUC7i5BN 00000032      01000013)
[    0.013076] ACPI: SSDT 0x000000007A7DE2D8 000EDE (v02 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013079] ACPI: LPIT 0x000000007A7DF1B8 000094 (v01 INTEL  NUC7i5BN 00000032 MSFT 0000005F)
[    0.013082] ACPI: WSMT 0x000000007A7DF250 000028 (v01 INTEL  NUC7i5BN 00000032 MSFT 0000005F)
[    0.013086] ACPI: SSDT 0x000000007A7DF278 000141 (v02 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013089] ACPI: SSDT 0x000000007A7DF3C0 00029F (v02 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013093] ACPI: SSDT 0x000000007A7DF660 003002 (v02 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013097] ACPI: DBGP 0x000000007A7E2668 000034 (v01 INTEL  NUC7i5BN 00000032 MSFT 0000005F)
[    0.013100] ACPI: DBG2 0x000000007A7E26A0 000054 (v00 INTEL  NUC7i5BN 00000032 MSFT 0000005F)
[    0.013103] ACPI: BGRT 0x000000007A7E26F8 000038 (v01 INTEL  NUC7i5BN 00000032 AMI  00010013)
[    0.013107] ACPI: DMAR 0x000000007A7E2730 0000A8 (v01 INTEL  NUC7i5BN 00000032 INTL 00000001)
[    0.013110] ACPI: NHLT 0x000000007A7E27D8 00002D (v00 INTEL  NUC7i5BN 00000032      01000013)
[    0.013114] ACPI: SSDT 0x000000007A7E2808 0001C9 (v01 INTEL  NUC7i5BN 00000032 INTL 20160422)
[    0.013117] ACPI: Reserving FACP table memory at [mem 0x7a7da100-0x7a7da213]
[    0.013119] ACPI: Reserving DSDT table memory at [mem 0x7a7b1210-0x7a7da0fb]
[    0.013120] ACPI: Reserving FACS table memory at [mem 0x7afbac40-0x7afbac7f]
[    0.013122] ACPI: Reserving APIC table memory at [mem 0x7a7da218-0x7a7da29b]
[    0.013123] ACPI: Reserving FPDT table memory at [mem 0x7a7da2a0-0x7a7da2e3]
[    0.013124] ACPI: Reserving MCFG table memory at [mem 0x7a7da2e8-0x7a7da323]
[    0.013125] ACPI: Reserving SSDT table memory at [mem 0x7a7da328-0x7a7da680]
[    0.013127] ACPI: Reserving FIDT table memory at [mem 0x7a7da688-0x7a7da723]
[    0.013128] ACPI: Reserving SSDT table memory at [mem 0x7a7da728-0x7a7dd89b]
[    0.013129] ACPI: Reserving HPET table memory at [mem 0x7a7dd8a0-0x7a7dd8d7]
[    0.013130] ACPI: Reserving SSDT table memory at [mem 0x7a7dd8d8-0x7a7de289]
[    0.013132] ACPI: Reserving UEFI table memory at [mem 0x7a7de290-0x7a7de2d1]
[    0.013133] ACPI: Reserving SSDT table memory at [mem 0x7a7de2d8-0x7a7df1b5]
[    0.013134] ACPI: Reserving LPIT table memory at [mem 0x7a7df1b8-0x7a7df24b]
[    0.013135] ACPI: Reserving WSMT table memory at [mem 0x7a7df250-0x7a7df277]
[    0.013137] ACPI: Reserving SSDT table memory at [mem 0x7a7df278-0x7a7df3b8]
[    0.013138] ACPI: Reserving SSDT table memory at [mem 0x7a7df3c0-0x7a7df65e]
[    0.013139] ACPI: Reserving SSDT table memory at [mem 0x7a7df660-0x7a7e2661]
[    0.013141] ACPI: Reserving DBGP table memory at [mem 0x7a7e2668-0x7a7e269b]
[    0.013142] ACPI: Reserving DBG2 table memory at [mem 0x7a7e26a0-0x7a7e26f3]
[    0.013143] ACPI: Reserving BGRT table memory at [mem 0x7a7e26f8-0x7a7e272f]
[    0.013144] ACPI: Reserving DMAR table memory at [mem 0x7a7e2730-0x7a7e27d7]
[    0.013146] ACPI: Reserving NHLT table memory at [mem 0x7a7e27d8-0x7a7e2804]
[    0.013147] ACPI: Reserving SSDT table memory at [mem 0x7a7e2808-0x7a7e29d0]
[    0.013156] ACPI: Local APIC address 0xfee00000
[    0.021520] ACPI: PM-Timer IO Port: 0x1808
[    0.021523] ACPI: Local APIC address 0xfee00000
[    0.021529] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.021531] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.021532] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.021533] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.021563] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.021565] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.021567] ACPI: IRQ0 used by override.
[    0.021569] ACPI: IRQ9 used by override.
[    0.021571] Using ACPI (MADT) for SMP configuration information
[    0.021572] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.080655] ACPI: Core revision 20210105
[    0.174457] PM: Registering ACPI NVS region [mem 0x6cdbf000-0x6cdbffff] (4096 bytes)
[    0.174457] PM: Registering ACPI NVS region [mem 0x7a7e3000-0x7afbafff] (8224768 bytes)
[    0.177255] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.177255] ACPI: bus type PCI registered
[    0.177255] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.178219] ACPI: Added _OSI(Module Device)
[    0.178219] ACPI: Added _OSI(Processor Device)
[    0.178219] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.178219] ACPI: Added _OSI(Processor Aggregator Device)
[    0.178219] ACPI: Added _OSI(Linux-Dell-Video)
[    0.178219] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.178219] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.233459] ACPI: 9 ACPI AML tables successfully acquired and loaded
[    0.242879] ACPI: Dynamic OEM Table Load:
[    0.242887] ACPI: SSDT 0xFFFF8CE1BCBA6000 00060F (v02 PmRef  Cpu0Ist  00003000 INTL 20160422)
[    0.244544] ACPI: \_PR_.CPU0: _OSC native thermal LVT Acked
[    0.246585] ACPI: Dynamic OEM Table Load:
[    0.246591] ACPI: SSDT 0xFFFF8CE36EDDA400 0003FF (v02 PmRef  Cpu0Cst  00003001 INTL 20160422)
[    0.248594] ACPI: Dynamic OEM Table Load:
[    0.248600] ACPI: SSDT 0xFFFF8CE1BCBA4800 00065C (v02 PmRef  ApIst    00003000 INTL 20160422)
[    0.250539] ACPI: Dynamic OEM Table Load:
[    0.250545] ACPI: SSDT 0xFFFF8CE000D7A800 000197 (v02 PmRef  ApHwp    00003000 INTL 20160422)
[    0.252029] ACPI: Dynamic OEM Table Load:
[    0.252035] ACPI: SSDT 0xFFFF8CE000D7A000 00018A (v02 PmRef  ApCst    00003000 INTL 20160422)
[    0.255838] ACPI: EC: EC started
[    0.255840] ACPI: EC: interrupt blocked
[    0.255864] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.255866] ACPI: \_SB_.PCI0.LPCB.H_EC: Boot DSDT EC used to handle transactions
[    0.255868] ACPI: Interpreter enabled
[    0.255922] ACPI: (supports S0 S3 S4 S5)
[    0.255923] ACPI: Using IOAPIC for interrupt routing
[    0.255974] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.257424] ACPI: Enabled 7 GPEs in block 00 to 7F
[    0.263100] ACPI: PM: Power Resource [WRST] (on)
[    0.263538] ACPI: PM: Power Resource [WRST] (on)
[    0.263977] ACPI: PM: Power Resource [WRST] (on)
[    0.264424] ACPI: PM: Power Resource [WRST] (on)
[    0.264862] ACPI: PM: Power Resource [WRST] (on)
[    0.265296] ACPI: PM: Power Resource [WRST] (on)
[    0.265729] ACPI: PM: Power Resource [WRST] (on)
[    0.266163] ACPI: PM: Power Resource [WRST] (on)
[    0.266598] ACPI: PM: Power Resource [WRST] (on)
[    0.267035] ACPI: PM: Power Resource [WRST] (on)
[    0.267474] ACPI: PM: Power Resource [WRST] (on)
[    0.267913] ACPI: PM: Power Resource [WRST] (on)
[    0.268353] ACPI: PM: Power Resource [WRST] (on)
[    0.268788] ACPI: PM: Power Resource [WRST] (on)
[    0.269228] ACPI: PM: Power Resource [WRST] (on)
[    0.269661] ACPI: PM: Power Resource [WRST] (on)
[    0.271498] ACPI: PM: Power Resource [WRST] (on)
[    0.271939] ACPI: PM: Power Resource [WRST] (on)
[    0.272374] ACPI: PM: Power Resource [WRST] (on)
[    0.273103] ACPI: PM: Power Resource [WRST] (on)
[    0.288495] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
[    0.289088] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
[    0.312006] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.312093] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
[    0.312173] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.312257] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.312336] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.312416] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.312495] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.312575] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.318768] ACPI: EC: interrupt unblocked
[    0.318770] ACPI: EC: event unblocked
[    0.318780] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.318781] ACPI: EC: GPE=0x14
[    0.318783] ACPI: \_SB_.PCI0.LPCB.H_EC: Boot DSDT EC initialization complete
[    0.318785] ACPI: \_SB_.PCI0.LPCB.H_EC: EC: Used to handle transactions and events
[    0.318857] PCI: Using ACPI for IRQ routing
[    0.354569] pnp: PnP ACPI init
[    0.355152] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.355491] pnp 00:01: Plug and Play ACPI device, IDs ITE8708 (active)
[    0.355690] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.355821] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.355867] system 00:04: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.356248] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.356333] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.356755] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.358534] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.359832] pnp: PnP ACPI: found 9 devices
[    2.057284] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330)
[    2.057339] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529)
[    2.057443] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330)
[    2.057484] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529)
[    2.057569] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330)
[    2.057610] ACPI Error: Aborting method \_PR.CPU3._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529)
[    2.382750] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    2.382761] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    2.382766] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    2.388004] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    2.388014] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    2.388019] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    3.788012] ACPI: bus type USB registered
[    4.319596] ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    6.640084] ACPI: button: Sleep Button [SLPB]
[    6.640992] ACPI: button: Power Button [PWRB]
[    6.655950] ACPI: button: Power Button [PWRF]
[    7.076054] pstore: On a broken BIOS, this can severely harm your system

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.12.2-vanilla root=UUID=dfbff61a-788e-4d2f-babf-2c95930448a6 splash=silent mitigations=auto quiet iommu=force intel_iommu=on
Comment 1 Paulo Marcos de Souza Arruda do Nascimento 2021-05-16 14:09:52 UTC
I'm having the exact same problem with Acer Aspire 5 A515-51-51UX, and the problem just appears with the latest kernel. If I use LTS kernel this acpi problem doesn't appear anymore. I will show my acpidump later when I finish installing arch on it.
Comment 2 Frank Kruger 2021-05-16 15:52:08 UTC
(In reply to Paulo Marcos de Souza Arruda do Nascimento from comment #1)
> I'm having the exact same problem with Acer Aspire 5 A515-51-51UX, and the
> problem just appears with the latest kernel.
Do you mean latest stable kernel 5.12.4?
Comment 3 MB 2021-05-17 14:07:36 UTC
Dear Maintainer,
also here the same error message since kernel 5.12.0 to 5.12.4
Debian Sid and Machine:   
Type: Desktop Mobo: ASRock model: KBL-NUC serial: N/A UEFI: American Megatrends v: P1.40B date: 12/15/2016 
CPU: Info: Dual Core model: Intel Core i3-7100U bits: 64 type: MT MCP L2 cache: 3 MiB
Comment 4 sander44 2021-05-19 08:37:36 UTC
This issue is reproduced with branch 5.10, version 5.10.32.
Comment 5 Paulo Marcos de Souza Arruda do Nascimento 2021-05-20 14:15:49 UTC
(In reply to Frank Kruger from comment #2)
> (In reply to Paulo Marcos de Souza Arruda do Nascimento from comment #1)
> > I'm having the exact same problem with Acer Aspire 5 A515-51-51UX, and the
> > problem just appears with the latest kernel.
> Do you mean latest stable kernel 5.12.4?

yes the latest stable kernel.
Comment 6 MB 2021-05-20 15:37:34 UTC
As long as no kernel maintainer answers, our confirmations are not of much use. Because it concerns acpi, it is probably ignored. Only version 5.11.xx is not affected yet.
Maybe there will be a patch after all. In 5.12.5 from 19.05.21 is still the same error.
Comment 7 Frank Kruger 2021-05-20 18:30:55 UTC
Maybe the linux-kernel list is more appropriate: https://marc.info/?l=linux-kernel&r=1&b=202105&w=2. Anyway, cc'ing Hans de Goede (@redhat), who might have an idea what's going on here.
Comment 8 Hans de Goede 2021-05-20 19:35:57 UTC
These kind of errors typically indicate that there is a bug in your ACPI tables (so this is a BIOS bug not a Linux bug). This is also why there are prefixed with: "ACPI BIOS Error (bug)".

Can people who are seeing this please attach an acpidump of their system here ?
Comment 9 Paulo Marcos de Souza Arruda do Nascimento 2021-05-21 00:32:56 UTC
Created attachment 296905 [details]
ACPIDUMP + DMESG outputs for linux and linux-lts

I am now providing ACPIDUMP and the output of 'sudo dmesg | grep ACPI > file' for both LTS and mainstream kernels, with latest updates from Arch Linux stable. Why did I provided two ACPIDUMP's? for some reason, the output of acpidump command is different between these kernels.
Since there's 4 files, i'm creating a .zip containing everything.
The laptop is an Acer Aspire 5 A515-51-51UX.
Comment 10 sander44 2021-05-21 17:33:33 UTC
Hi MB and all,

I reproduced this issue with 5.10.35.

Attached my acpidump zipfile on this ticket.

>> acpidump-5.10.35-1.zip

Thanks.
Comment 11 sander44 2021-05-21 17:34:24 UTC
Created attachment 296919 [details]
acpidump-5.10.35-1.zip - acpidump
Comment 12 MB 2021-05-22 12:01:19 UTC
(In reply to Hans de Goede from comment #8)
> These kind of errors typically indicate that there is a bug in your ACPI
> tables (so this is a BIOS bug not a Linux bug). This is also why there are
> prefixed with: "ACPI BIOS Error (bug)".

Yes, that is known. But nevertheless there must be a difference in the query to kernel 5.11.x, because there this error message is not present.

regards
MB
Comment 13 Paulo Marcos de Souza Arruda do Nascimento 2021-05-28 22:49:24 UTC
On my desktop with ryzen 1600AF + asus ex-a320m-gaming, these acpi errors didn't appear, but on my work computer it does too. both my laptop and work computer shows these acpi errors and those have intel CPU's. maybe it's an intel-related stuff
Comment 14 Juhász Péter Károly 2021-06-03 12:01:12 UTC
Same here: MSI MPG Z390 Gaming Pro Carbon
Comment 15 Juhász Péter Károly 2021-06-03 12:07:02 UTC
Created attachment 297135 [details]
MSI MPG Z390 Gaming Pro Carbon acpidump
Comment 16 Hans de Goede 2021-06-03 14:31:30 UTC
Ok, so I've removed the timestamps from the 2 dmesg logs attached by Paulo Marcos and then ran a diff -u, after that I edited out some (non-relevant) memory-address differences and did a second diff -u, this results in this:

--- dmesg_5.10.38-1-lts	2021-06-03 16:29:41.372922210 +0200
+++ dmesg_linux-5.12.5-arch1-1	2021-06-03 16:30:01.013031634 +0200
@@ -92,7 +92,7 @@
 ACPI: IRQ9 used by override.
 Using ACPI (MADT) for SMP configuration information
 ACPI: HPET id: 0x8086a201 base: 0xfed00000
-ACPI: Core revision 20200925
+ACPI: Core revision 20210105
 PM: Registering ACPI NVS region [mem 0x7156c000-0x7156cfff] (4096 bytes)
 PM: Registering ACPI NVS region [mem 0x8a88f000-0x8af7efff] (7274496 bytes)
 ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
@@ -113,10 +113,6 @@
 ACPI: Dynamic OEM Table Load:
 ACPI: SSDT 0xFFFF... 0003FF (v02 PmRef  Cpu0Cst  00003001 INTL 20160527)
 ACPI: Dynamic OEM Table Load:
-ACPI: SSDT 0xFFFF... 0000BA (v02 PmRef  Cpu0Hwp  00003000 INTL 20160527)
-ACPI: Dynamic OEM Table Load:
-ACPI: SSDT 0xFFFF... 000628 (v02 PmRef  HwpLvt   00003000 INTL 20160527)
-ACPI: Dynamic OEM Table Load:
 ACPI: SSDT 0xFFFF... 000D14 (v02 PmRef  ApIst    00003000 INTL 20160527)
 ACPI: Dynamic OEM Table Load:
 ACPI: SSDT 0xFFFF... 000317 (v02 PmRef  ApHwp    00003000 INTL 20160527)

(there are other differences later during boots, but these are the ones which count).

So for some reason the kernel is no longer loading the Cpu0Hwp and HwpLvt SSDT-s, and that is causing these errors.
Comment 17 Hans de Goede 2021-06-03 15:01:27 UTC
sander44:
> I reproduced this issue with 5.10.35.

So you mean you are seeing the "Could not resolve symbol [\_PR.CPU0._CPC]" errors with 5.10.35, correct ?  That is interesting because for Paulo Marcos these errors are no happening with 5.10.38 .  Can you perhaps give 5.10.38 a try ?

A suspect that this may have something to do with these 2 commits:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6998a8800d73116187aad542391ce3b2dd0f9e30
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1a1c130ab7575498eed5bcf7220037ae09cd1f8a

Can someone who is seeing this try building a 5.12 kernel with these 2 commits reverted please? Note you should revert the 6998a8800d73116187aad commit first.
Comment 18 Paulo Marcos de Souza Arruda do Nascimento 2021-06-03 18:47:00 UTC
(In reply to Hans de Goede from comment #17)
> sander44:
> > I reproduced this issue with 5.10.35.
> 
> So you mean you are seeing the "Could not resolve symbol [\_PR.CPU0._CPC]"
> errors with 5.10.35, correct ?  That is interesting because for Paulo Marcos
> these errors are no happening with 5.10.38 .  Can you perhaps give 5.10.38 a
> try ?
> 
> A suspect that this may have something to do with these 2 commits:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=6998a8800d73116187aad542391ce3b2dd0f9e30
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=1a1c130ab7575498eed5bcf7220037ae09cd1f8a
> 
> Can someone who is seeing this try building a 5.12 kernel with these 2
> commits reverted please? Note you should revert the 6998a8800d73116187aad
> commit first.

I will compile this kernel right now by installing linux-git package (arch linux)
Comment 19 Paulo Marcos de Souza Arruda do Nascimento 2021-06-03 18:53:36 UTC
but first I will figure out how to revert these commits. I will probably take a little bit longer to show some results
Comment 20 sander44 2021-06-04 05:18:05 UTC
Hi @all,

I recompile kernel version 5.10.35 vanilla and not observe this issue.
This issue is view in 5.12 branch.
Comment 21 Paulo Marcos de Souza Arruda do Nascimento 2021-06-04 20:54:59 UTC
(In reply to Hans de Goede from comment #17)
> sander44:
> > I reproduced this issue with 5.10.35.
> 
> So you mean you are seeing the "Could not resolve symbol [\_PR.CPU0._CPC]"
> errors with 5.10.35, correct ?  That is interesting because for Paulo Marcos
> these errors are no happening with 5.10.38 .  Can you perhaps give 5.10.38 a
> try ?
> 
> A suspect that this may have something to do with these 2 commits:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=6998a8800d73116187aad542391ce3b2dd0f9e30
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=1a1c130ab7575498eed5bcf7220037ae09cd1f8a
> 
> Can someone who is seeing this try building a 5.12 kernel with these 2
> commits reverted please? Note you should revert the 6998a8800d73116187aad
> commit first.

If I apply one patch, the other one refuses to apply itself. I'm applying the first one to see if there's any difference
Comment 22 MB 2021-06-05 12:02:10 UTC
(In reply to Hans de Goede from comment #17)

> A suspect that this may have something to do with these 2 commits:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=6998a8800d73116187aad542391ce3b2dd0f9e30
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=1a1c130ab7575498eed5bcf7220037ae09cd1f8a
> 
> Can someone who is seeing this try building a 5.12 kernel with these 2
> commits reverted please? Note you should revert the 6998a8800d73116187aad
> commit first.
The same error with both commits and 5.12.9 too.
The LTS 5.10.42 works ok without ACPI errors.

regards
MB
Comment 23 Paulo Marcos de Souza Arruda do Nascimento 2021-06-05 13:34:33 UTC
I tried to compile and install the linux (git, since these commits are for 5.13-rc5 kernel) with these commits reversed, but I had no success while installing it (make modules_install was complaining about missing stuff, even if I install without the patches), so I coudn't test it.
But anyway I tried the latest LTS and stable kernels (5.10.42 and 5.12.9) and the stable one tells me the same ACPI errors, while LTS don't.
Comment 24 Hans de Goede 2021-06-07 09:41:28 UTC
Good news, a very similar bug is being tracked here:

https://bugzilla.redhat.com/show_bug.cgi?id=1963717

And one of the reporters there has done a git bisect and has found the commit which is causing the problem for them:

"""
git-bisect points to 719e1f561afbe020ed175825a9bd25ed62ed1697 :
"ACPI: Execute platform _OSC also with query bit clear".

Tested 5.12.9 kernel with the commit reverted, and confirmed that the error
messages are gone. (I had to revert
5a6a2c0f0f43676df27632d657a3f18b151a7ef8 for dependency too.)

It also brings back the /sys/devices/system/cpu/cpu0/acpi_cppc which is absent
in the stable 5.12.x

Hope this helps
"""

Can some one seeing the "Could not resolve symbol [\_PR.CPU0._CPC]" error try building a 5.12 kernel with the 719e1f561afbe020ed175825a9bd25ed62ed1697 commit reverted and see of that helps please?
Comment 25 Hans de Goede 2021-06-07 09:49:12 UTC
Note as mentioned in the quoted comment to revert 719e1f561afbe020ed175825a9bd25ed62ed1697 you first need to revert 5a6a2c0f0f43676df27632d657a3f18b151a7ef8

So after doing a clean checkout of the 5.12.y branch you need to run:

git revert 5a6a2c0f0f43676df27632d657a3f18b151a7ef8
git revert 719e1f561afbe020ed175825a9bd25ed62ed1697

And then build + install the kernel after that.
Comment 26 Hans de Goede 2021-06-07 10:06:24 UTC
Created attachment 297195 [details]
[PATCH] ACPI: Use _OSC query results to determine caps rather then the commit results

I've taken a quick look at commit 719e1f561afb ("ACPI: Execute platform _OSC also with query bit clear") and I think I may have found the problem.

Please test a 5.12 kernel with the patch which I've just attached.

If this patch does *not* help, then please let me know if reverting commit 719e1f561afb helps.
Comment 27 MB 2021-06-07 13:50:15 UTC
(In reply to Hans de Goede from comment #26)
> 
> Please test a 5.12 kernel with the patch which I've just attached.
>
No, with the patch the error is unfortunately still present. 
> If this patch does *not* help, then please let me know if reverting commit
> 719e1f561afb helps.
Please send the complete download link to the commit.

regards
MB
Comment 28 sander44 2021-06-07 16:25:22 UTC
My fix working with 5.10 branch:

index c49b35e30..cdff9cb03 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -332,39 +332,22 @@ static void acpi_bus_osc_negotiate_platform_control(void)
 	if (ACPI_FAILURE(acpi_get_handle(NULL, "\\_SB", &handle)))
 		return;
 
-	if (ACPI_FAILURE(acpi_run_osc(handle, &context)))
-		return;
-
-	capbuf_ret = context.ret.pointer;
-	if (context.ret.length <= OSC_SUPPORT_DWORD) {
+	if (ACPI_SUCCESS(acpi_run_osc(handle, &context))) {
+		capbuf_ret = context.ret.pointer;
+		if (context.ret.length > OSC_SUPPORT_DWORD) {
+			osc_sb_apei_support_acked =
+				capbuf_ret[OSC_SUPPORT_DWORD] & OSC_SB_APEI_SUPPORT;
+			osc_pc_lpi_support_confirmed =
+				capbuf_ret[OSC_SUPPORT_DWORD] & OSC_SB_PCLPI_SUPPORT;
+			osc_sb_native_usb4_support_confirmed =
+				capbuf_ret[OSC_SUPPORT_DWORD] & OSC_SB_NATIVE_USB4_SUPPORT;
+		}
 		kfree(context.ret.pointer);
-		return;
-	}
-
-	/*
-	 * Now run _OSC again with query flag clean and with the caps
-	 * both platform and OS supports.
-	 */
-	capbuf[OSC_QUERY_DWORD] = 0;
-	capbuf[OSC_SUPPORT_DWORD] = capbuf_ret[OSC_SUPPORT_DWORD];
-	kfree(context.ret.pointer);
-
-	if (ACPI_FAILURE(acpi_run_osc(handle, &context)))
-		return;
-
-	capbuf_ret = context.ret.pointer;
-	if (context.ret.length > OSC_SUPPORT_DWORD) {
-		osc_sb_apei_support_acked =
-			capbuf_ret[OSC_SUPPORT_DWORD] & OSC_SB_APEI_SUPPORT;
-		osc_pc_lpi_support_confirmed =
-			capbuf_ret[OSC_SUPPORT_DWORD] & OSC_SB_PCLPI_SUPPORT;
-		osc_sb_native_usb4_support_confirmed =
-			capbuf_ret[OSC_SUPPORT_DWORD] & OSC_SB_NATIVE_USB4_SUPPORT;
 	}
-
-	kfree(context.ret.pointer);
+	/* do we need to check other returned cap? Sounds no */
 }
 
+
 /*
  * Native control of USB4 capabilities. If any of the tunneling bits is
  * set it means OS is in control and we use software based connection
-- 
2.30.2
Comment 29 Hans de Goede 2021-06-07 19:02:39 UTC
(In reply to sander44 from comment #28)
> My fix working with 5.10 branch:

I assume you mean the 5.12 branch, the code which your patch is removing does not exist in the 5.10 branch.

This is basically the earlier mentioned revert of commit 5a6a2c0f0f43676df27632d657a3f18b151a7ef8 and commit 719e1f561afbe020ed175825a9bd25ed62ed1697.

Thank you for confirming that undoing the changes from 719e1f561afbe020ed175825a9bd25ed62ed1697 fixes the "[\_PR.CPU0._CPC], AE_NOT_FOUND" errors.
Comment 30 Hans de Goede 2021-06-07 19:05:54 UTC
sander44, have you also tried using my patch instead of reverting the changes from 719e1f561afbe020ed175825a9bd25ed62ed1697 ?  And if not can you give this a try please ?
Comment 31 Hans de Goede 2021-06-08 09:47:19 UTC
Created attachment 297231 [details]
[PATCH] ACPI: Only run _OSC without the query flag on machines with native USB4 support

Everyone, thank you for all the testing.

Here is a new patch for 5.12 / 5.13 which should fix this, please give this patch a try and let me know if this fixes things.
Comment 32 MB 2021-06-08 11:14:13 UTC
(In reply to Hans de Goede from comment #31)
> Here is a new patch for 5.12 / 5.13 which should fix this, please give this
> patch a try and let me know if this fixes things.

Yes, now the error is gone.
Thank you very much and

regards
MB
Comment 33 Hans de Goede 2021-06-08 17:15:21 UTC
Created attachment 297241 [details]
[PATCH] ACPI: Pass the same capabilities to the _OSC regardless of the query flag

Thank you for testing my patch and for confirming that the new version fixes things.

Discussion with the upstream ACPI maintainers has resulted in a different approach / patch which should also fix this. I'm attaching a new patch using this new approach, can you please give this new patch a try ?

Sorry for all the different patches / all the testing requests. This last one should be the final patch, assuming it does indeed fix things.
Comment 34 MB 2021-06-08 18:50:16 UTC
(In reply to Hans de Goede from comment #33)

>This last one should be the final patch, assuming it does indeed fix things.

Even with the latest patch, the error no longer occurs.

regards
MB
Comment 35 Hans de Goede 2021-06-09 16:09:32 UTC
Thank you for testing, the latest version of the patch has been accepted by Rafael (the ACPI subsystem maintainer) and should show up in a 5.13-rc# release soon, once it hits 5.13-rc# and it should get cherry picked into a 5.12.y stable release soon after that, closing this.
Comment 36 John Humes 2022-03-13 08:36:43 UTC
Apparently, the bug still persists for me. Using vanilla linux kernel 5.15.12 compiled from source on my Gentoo on Thinkpad T440s. The problem emerges when I try to hibernate my laptop: it attempts to, but ends up rebooting itself with the following errors in dmesg. I might be mistaking this for a different bug altogether or my misconfiguration of the kernel, but I'd really like if somebody were to assess the problem.
Comment 37 John Humes 2022-03-13 08:38:07 UTC
Created attachment 300560 [details]
T440s dmesg

If you need anything else, I'll be glad to upload it.
Comment 38 MB 2022-04-09 15:02:26 UTC
Dear Maintainer,

The error is unfortunately back with kernel 5.15.33. Was something changed in this version?
After applying the patch, the error has disappeared.
I ask the maintainer to check.

Best regards
MB
Comment 39 Takashi Iwai 2022-04-20 07:22:27 UTC
The fix was reverted recently in the upstream commit 2ca8e6285250 (which was backported to stable trees, too), hence the problem resurfaced.
That said, we came back to square.
Comment 40 Lethe 2022-04-27 09:36:22 UTC
Created attachment 300819 [details]
acpidump + dmesg - 5.17.4

Added acpidump && dmesg | grep -i acpi

for Kaby Lake CPU on Intel B250
booting 5.17.4
Comment 41 Max 2022-04-29 12:15:56 UTC
Same here:
```
[    0.767033] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[    0.767180] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
```
Kernel 5.17.5
Comment 42 Mario Limonciello (AMD) 2022-06-23 13:36:13 UTC
Can you please try to cherry-pick https://github.com/torvalds/linux/commit/c42fa24b44751c62c86e98430ef915c0609a2ab8 into your 5.17.x based kernel?
Comment 43 MB 2022-06-26 15:00:03 UTC
(In reply to Mario Limonciello (AMD) from comment #42)
> Can you please try to cherry-pick
> https://github.com/torvalds/linux/commit/
> c42fa24b44751c62c86e98430ef915c0609a2ab8 into your 5.17.x based kernel?

Just for info, the kernel 5.17 is EOL since 14.06.22.
Comment 44 Zhang Rui 2022-06-27 03:57:03 UTC
*** Bug 215830 has been marked as a duplicate of this bug. ***
Comment 45 Zhang Rui 2022-06-27 04:03:08 UTC
please confirm applying the commit in comment #42 on top of 5.17 kernel fix the problem.
please confirm the problem doesn't exist in the latest upstream kernel.
Comment 46 Zhang Rui 2022-06-27 04:20:54 UTC
*** Bug 216169 has been marked as a duplicate of this bug. ***
Comment 47 Zhang Rui 2022-06-28 01:34:35 UTC
*** Bug 216070 has been marked as a duplicate of this bug. ***
Comment 48 CUI Hao 2022-06-28 15:55:19 UTC
Created attachment 301297 [details]
acpidump, ASRock B460M-ITX/ac (P1.60 BIOS) motherboard + Intel Core i7-10700K CPU

Redirected to this issue from Bug 216070.

Confirmed that c42fa24b44751c62c86e98430ef915c0609a2ab8 doesn't fix my errors.
Comment 49 Mario Limonciello (AMD) 2022-06-29 02:10:48 UTC
Can someone affected see if below makes the error "go away" on top of 5.19-rcX?

diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index 86fa61a21826..94c72e342297 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -358,11 +358,6 @@ static void acpi_bus_osc_negotiate_platform_control(void)
                return;
        }
 
-#ifdef CONFIG_ACPI_CPPC_LIB
-       osc_sb_cppc_not_supported = !(capbuf_ret[OSC_SUPPORT_DWORD] &
-                       (OSC_SB_CPC_SUPPORT | OSC_SB_CPCV2_SUPPORT));
-#endif
-
        /*
         * Now run _OSC again with query flag clear and with the caps
         * supported by both the OS and the platform.
@@ -376,6 +371,10 @@ static void acpi_bus_osc_negotiate_platform_control(void)
 
        capbuf_ret = context.ret.pointer;
        if (context.ret.length > OSC_SUPPORT_DWORD) {
+#ifdef CONFIG_ACPI_CPPC_LIB
+               osc_sb_cppc_not_supported = !(capbuf_ret[OSC_SUPPORT_DWORD] &
+                               (OSC_SB_CPC_SUPPORT | OSC_SB_CPCV2_SUPPORT));
+#endif
                osc_sb_apei_support_acked =
                        capbuf_ret[OSC_SUPPORT_DWORD] & OSC_SB_APEI_SUPPORT;
                osc_pc_lpi_support_confirmed =
Comment 50 CUI Hao 2022-06-30 03:57:07 UTC
(In reply to Mario Limonciello (AMD) from comment #49)
> Can someone affected see if below makes the error "go away" on top of
> 5.19-rcX?
> 

I observed the same error message after applying the patch on top of 5.19-rc4.
(Note that I came from Bug 216070 so the errors are kind of different from this thread).
Comment 51 Mario Limonciello (AMD) 2022-06-30 04:00:54 UTC
OK thanks for trying it.  Can you please provide your acpidump?  I would like to see two acpidumps - one reproducing the issue, and one reverting the revert commit.
Comment 52 Mario Limonciello (AMD) 2022-06-30 15:18:22 UTC
Created attachment 301313 [details]
patch with potential fix + more debugging messages

Here is another stab at a patch.  Hopefully this fixes the problem, but it also has a bunch of debugging messages.  Anyone who tries it, please share a full dmesg (failure or not).
Comment 53 CUI Hao 2022-06-30 17:32:48 UTC
Created attachment 301316 [details]
My acpidump & kernel messages (ASRock B460M-ITX/ac (P1.60 BIOS) motherboard + Intel Core i7-10700K CPU)

(In reply to Mario Limonciello (AMD) from comment #52)
> Here is another stab at a patch.  Hopefully this fixes the problem, but it
> also has a bunch of debugging messages.  Anyone who tries it, please share a
> full dmesg (failure or not).

Still doesn't fix my errors. My acpidump & kernel messages (with vanilla 5.19.0-rc4 kernel and patched one) are attached. It looks like the only relevant log is: `ACPI: Negotiated _OSC: 59`
Comment 54 Mario Limonciello (AMD) 2022-06-30 18:04:43 UTC
Created attachment 301317 [details]
patch with potential fix: Only let cppc_acpi run if CPPCv2 was not masked

OK, it looks like the SSDT only loads if CPPCv2 was acked, which in your system only CPPCv1 was acked.

>>> result = 59
>>> result & OSC_SB_CPCV2_SUPPORT
0
>>> result & OSC_SB_CPC_SUPPORT
32

Try this updated patch which won't let it probe _CPC further in that specific case.
Comment 55 CUI Hao 2022-06-30 21:59:01 UTC
(In reply to Mario Limonciello (AMD) from comment #54)
> Try this updated patch which won't let it probe _CPC further in that
> specific case.

Yeah I confirm the latest patch makes my errors go away.
Comment 56 Mario Limonciello (AMD) 2022-07-01 02:34:36 UTC
Thanks.  I've submitted a cleaned up version as https://lore.kernel.org/linux-acpi/20220701022529.2134-1-mario.limonciello@amd.com/T/#m1315cf888451d63578a40bedfae687e419b6bb56
If you can test that final version and leave a Tested-by tag, would be appreciated.
Comment 57 Takehiko Abe 2022-07-12 12:13:10 UTC
This is not good. The patch does eliminate the error messages for me, but it also disables CPPC on my system. 

My board is ASRock H470 Phantom Gaming 4, BIOS L1.12 12/04/2020.

The board bios has a config for "Intel Speed Shift Technology". The user manual says this about it:

"Enable/Disable Intel Speed Shift Technology support. Enabling will expose the CPPC v2 interface to allow for hardware controlled P-sates."

When I first got the error messages with 5.12.6 last year, I confirmed that the error messages disappears with CPPC v2 option disabled. But disabling CPPC v2 support is not a way to go, I guess?

I believe ASRock B460M also supports CPPCv2.
Comment 58 Mario Limonciello (AMD) 2022-07-12 14:41:14 UTC
Are you sure it actually worked before?  The firmware masking it does not give me confidence it really worked.
Comment 59 CUI Hao 2022-07-12 14:58:43 UTC
(In reply to Takehiko Abe from comment #57)
> "Enable/Disable Intel Speed Shift Technology support. Enabling will expose
> the CPPC v2 interface to allow for hardware controlled P-sates."
> 
> When I first got the error messages with 5.12.6 last year, I confirmed that
> the error messages disappears with CPPC v2 option disabled. But disabling
> CPPC v2 support is not a way to go, I guess?
> 
> I believe ASRock B460M also supports CPPCv2.

I mentioned the same observation in Bug 216070 that acpi_cppc interface is gone. I just looked my ASRock B460M-ITX's firmware settings. You are right, the option "Enable/Disable Intel Speed Shift Technology support" has the same help message.

But I don't know if the bug / current fix disables any function that had worked before. Based on various online resources, my understanding is "Intel Speed Shift" = HWP (Hardware P-state) in Linux, and I can see kernel message say it always works (intel_pstate: HWP enabled).

(In reply to Mario Limonciello (AMD) from comment #58)
> Are you sure it actually worked before?  The firmware masking it does not
> give me confidence it really worked.

I can confirm /sys/devices/system/cpu/cpuX/acpi_cppc/ exists before 5.17.2 when the error hadn't been introduced. But I don't know if things in it were actually usable. Is there anything I can do to test if CPPCv2 works on old kernels?
Comment 60 Mario Limonciello (AMD) 2022-07-12 15:48:57 UTC
> Is there anything I can do to test if CPPCv2 works on old kernels?

Maybe Rui can comment on that question.
Comment 61 Takehiko Abe 2022-07-13 09:34:07 UTC
(In reply to Mario Limonciello (AMD) from comment #58)
> Are you sure it actually worked before?  The firmware masking it does not
> give me confidence it really worked.

I run the system with 5.18.10 with the original patch (the reverted one) applied.

It has /sys/devices/system/cpu/cpu0/acpi_cppc entry. But, no, I am not sure if CPPCv2 is actually working or not. ouch.
Comment 62 neoglez 2022-07-20 10:16:55 UTC
Hi, the same problem here. Ubuntu 20.04.4 LTS with kernel 5.15.0-41-generic.
Comment 63 Manuel Lauss 2022-07-22 06:25:48 UTC
This patch also disables CPPC support on a few of my relatively recent AMD Zen Desktop systems. The issue is that the ACPI _OSC method supports ONLY the UUID of the "PCI root bridge device", but not any other, but linux is looking for CPPC support with the "Platform-Wide OSPM Capabilities" uuid, which does not
exist anywhere in the firmware.  bios engineers told me that this is all part of AMDs AGESA thingie, and they won't be able to add support for this, at least
on current (i.e. zen3-supporting) platforms.

Could this be worked around, by first checking whether any _CPC objects exist, and maybe a matching PCC entry?
Comment 64 Manuel Lauss 2022-07-22 09:05:42 UTC
(In reply to Manuel Lauss from comment #63)
> This patch also disables CPPC support on a few of my relatively recent AMD
> Zen Desktop systems. The issue is that the ACPI _OSC method supports ONLY
> the UUID of the "PCI root bridge device", but not any other, but linux is
> looking for CPPC support with the "Platform-Wide OSPM Capabilities" uuid,
> which does not
> exist anywhere in the firmware.  bios engineers told me that this is all
> part of AMDs AGESA thingie, and they won't be able to add support for this,
> at least
> on current (i.e. zen3-supporting) platforms.
> 
> Could this be worked around, by first checking whether any _CPC objects
> exist, and maybe a matching PCC entry?

Oh I see this was fixed recently with 
fbd74d16  ("ACPI: CPPC: Fix enabling CPPC on AMD systems with shared memory").
Comment 65 neoglez 2022-07-22 09:33:34 UTC
Just to add that I have a Z270 Tomahawk MB with an Intel® Core™ i7-10510Y Processor (8M Cache, up to 4.50 GHz).
Comment 66 Mario Limonciello (AMD) 2022-07-22 13:17:50 UTC
All the known issues from CPPC and _OSC with AMD should be fixed for 5.19-rc8.  If you still have one with Zen open a new issue.

The remaining issue is that reportedly from this thread a number of Intel systems the firmware will mask the _OSC during negotiation.  When the _OSC is masked a dynamic SSDT doesn't get loaded.

Someone needs to confirm if:
* This is intended behavior that firmware masks the _OSC (and thus CPPC v2 shouldn't be used on these systems).
or 
* This is purely a firmware bug and CPPC v2 should be used and that should be quirked when the _OSC is evaluated on the affected systems (or later so the SSDT still loads).
Comment 67 EdiD 2022-07-23 08:12:47 UTC
On intel platform with upstream 5.15.55 kernel and distro 5.18.5 kernel:

ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
(..)
Comment 68 sparks71 2022-07-23 15:59:37 UTC
here the same

[    0.332185] ACPI: button: Power Button [PWRF]
[    0.332299] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210730/psargs-330)

[    0.332308] No Local Variables are initialized for Method [_CPC]

[    0.332310] No Arguments are initialized for method [_CPC]

[    0.332311] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.332344] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210730/psargs-330)

[    0.332349] No Local Variables are initialized for Method [_CPC]

[    0.332350] No Arguments are initialized for method [_CPC]

[    0.332352] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.332389] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210730/psargs-330)

[    0.332394] No Local Variables are initialized for Method [_CPC]

[    0.332395] No Arguments are initialized for method [_CPC]

[    0.332397] ACPI Error: Aborting method \_PR.CPU3._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.332848] thermal LNXTHERM:00: registered as thermal_zone0

Ubuntu 20.04.4 LTS
5.15.0-41-generic 

MSI Z270 SLI Plus
Intel(R) Core(TM) i5-7600
Comment 69 EdiD 2022-08-02 15:42:02 UTC
Looks like it is fixed. These errors:

ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
(..)

are gone on intel platform with kernel 5.18.14
Comment 70 arthur 2022-08-21 10:08:36 UTC
Lenovo Thinkpad P14s AMD Gen2
still errors here:

[    0.449031] ACPI BIOS Error (Bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.AC._PSR.AFN4], AE_NOT_FOUND (20220331/psargs-330)
[    0.449046] ACPI Error: Abotrting method \_SB.PCI0.LPC0.EC0.AC._PSR due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

Kernel: Linux 5.19.2-arch1-1
Comment 71 Mario Limonciello (AMD) 2022-08-21 12:51:27 UTC
Arthur your issues are different. Open your own issue and be sure to attach a full log and details of the regression:
which BIOS or which kernel introduced it

If it's not a regression you should report it to Lenovo.
Comment 72 arthur 2022-08-21 13:24:45 UTC
@mario, thanks for your answer. i opened an new issue: https://bugzilla.kernel.org/show_bug.cgi?id=216390
Comment 73 Taku 2022-09-23 10:12:00 UTC
Model Name: ASUS ZenBook13 UX325J
BIOS Version: 311
CPU: Intel Core(TM) i7-10 65G7 CPU @ 1.30GHz
GPU: Intel Iris(R) Plus Graphics
OS: Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-48-generic x86_64) / Windows 11

I made 'sudo apt-get dist-upgrade' on 22-Sep-2022, followed by I lost an access to Ubuntu GUI.
Everytime I try to login, following error message is shown and only tty access is available.

-------------------------- Error message --------------------------
[  0.076056] x86/cpu: SGX disabled by BIOS.
[  0.130860] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.I2CO.TPDO], AE_NOT_FOUND (20210730/dswload2-162)
[  0.130868] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
[  0.130895] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.I2C1.TPL1], AE_NOT_FOUND (20210730/dswload2-162)
[  0.130898] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
[  0.561376] pci 0000:00:07.0: DPC: RP PI0 log size 0 is invalid
[  0.563606] pci 0000:00:07.1: DPC: RP PI0 log size 0 is invalid
/dev/nvme0n1p4: clean, 604301/22405120 files, 35951873/89599744 blocks
[  1.862340] mtd device must be supplied (device name is empty)
[  2.167925] mtd device must be supplied (device name is empty)
[  2.369446] mtd device must be supplied (device name is empty)
[  4.033184] ucsi_acpi USBC000:00: PPN init failed (-110)
Comment 74 tele 2022-11-11 13:33:26 UTC
I have a similar error " [\_PR.CPU0._CPC], AE_NOT_FOUND ".
I don't expect that kernel will always compatible with my ACPI.
Because now that's my second array mismatch error.
The problem is that, based on the error above, I don't know which module I need disable.
At least until the new kernel will updated.
I can only off the entire ACPI or ignore the error.

Question.
- I suppose when I will have old equipment I will have more errors.
Can I count on being able to disable what doesn't work with the kernel table in the future?
I need an extra message / information on how / what I can turn this off.
Comment 75 Taku 2022-11-11 13:44:22 UTC
The only solution worked for me was to re-install same version of ubuntu into same partition. 
If you UNCHECK 'Format' option on installation process, your personal files will survive after re-installation.

Note You need to log in before you can comment on or make changes to this bug.