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.

(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?

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

This issue is reproduced with branch 5.10, version 5.10.32.

(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.

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.

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.

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 ?

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.

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.

Created attachment 296919 [details]
acpidump-5.10.35-1.zip - acpidump

(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

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

Same here: MSI MPG Z390 Gaming Pro Carbon

Created attachment 297135 [details]
MSI MPG Z390 Gaming Pro Carbon acpidump

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.

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.

(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)

but first I will figure out how to revert these commits. I will probably take a little bit longer to show some results

Hi @all,

I recompile kernel version 5.10.35 vanilla and not observe this issue.
This issue is view in 5.12 branch.

(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

(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

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.

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?

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.

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.

(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

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

(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.

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 ?

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.

(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

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.

(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

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.

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.

Created attachment 300560 [details]
T440s dmesg

If you need anything else, I'll be glad to upload it.

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

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.

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

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

Can you please try to cherry-pick https://github.com/torvalds/linux/commit/c42fa24b44751c62c86e98430ef915c0609a2ab8 into your 5.17.x based kernel?

(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.

*** Bug 215830 has been marked as a duplicate of this bug. ***

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.

*** Bug 216169 has been marked as a duplicate of this bug. ***

*** Bug 216070 has been marked as a duplicate of this bug. ***

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.

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 =

(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).

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.

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).

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`

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.

(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.

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.

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.

Are you sure it actually worked before?  The firmware masking it does not give me confidence it really worked.

(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?

> Is there anything I can do to test if CPPCv2 works on old kernels?

Maybe Rui can comment on that question.

(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.

Hi, the same problem here. Ubuntu 20.04.4 LTS with kernel 5.15.0-41-generic.

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?

(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").

Just to add that I have a Z270 Tomahawk MB with an Intel® Core™ i7-10510Y Processor (8M Cache, up to 4.50 GHz).

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).

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)
(..)

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

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

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

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.

@mario, thanks for your answer. i opened an new issue: https://bugzilla.kernel.org/show_bug.cgi?id=216390

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)

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.

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.

It is January 2023 now, and this bug is still active in kernel 5.15.86. :(

I am running KDE Neon with self compiled kernel 5.15.x (because it is marked as "longterm") on a Fujitsu mainboard, equipped with an Intel Core i5. (See below.)

I wouldn't mind having these messages in the systemlog, as they are harmless and the system runs without any quirk. But but they appear on the console as well, even interrupting the splash screen! (Which is a bit of a humiliation, if there's a Windows user looking over your shoulder while your machine is booting...)

I know that this is a pure cosmetic complain, but it has been happening for more than a year now, and I really would like to get rid of this annoyance. I tried the usual grub command line options like 

"loglevel=3" 

"acpi_osi=! \"acpi_osi=Windows 2015\""

but neither did suppress these console messages. 


Hardware information:

~$  LC_ALL="C" sudo dmidecode -t 2
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.

Handle 0x0043, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: FUJITSU
        Product Name: D3431-A1
        Version: S26361-D3431-A1            
        Serial Number: 51857501
        Asset Tag:                       
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis:                       
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0


~$ LC_ALL="C" lscpu 
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  4
  On-line CPU(s) list:   0-3
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    CPU family:          6
    Model:               94
    Thread(s) per core:  1
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            3
    CPU max MHz:         3600.0000
    CPU min MHz:         800.0000
    BogoMIPS:            6399.96
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts ac
                         pi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_p
                         erfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dte
                         s64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2
                         apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefet
                         ch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriorit
                         y ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx 
                         smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hw
                         p_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
...

Sorry, I forgot to include the exact messages! These are the messages that appear in the systemlog and on the console, interrupting the splash screen:


[    0.857051] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330)
[    0.858519] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.859946] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330)
[    0.861572] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.863666] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330)
[    0.865063] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.866642] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330)
[    0.868458] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

Hello,

Sorry if I'm posting this wrong, but I get the same error, using Linux Mint kernel version 5.4.0-137 on HP Elitebook 745
I installed the latest: 5.4.0-144 and the issue still persists. 
It's not only that the messages appear on the console, but actually takes several restarts (using the button) to load the system.

# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.1.0 present.

Handle 0x0011, DMI type 2, 17 bytes
Base Board Information
	Manufacturer: HP
	Product Name: 83D5
	Version: KBC Version 08.61.00
	Serial Number: PGWJE00WBCO144
	Asset Tag:  
	Features:
		Board is a hosting board
	Location In Chassis:  
	Chassis Handle: 0x0000
	Type: Motherboard
	Contained Object Handles: 0

#lscpu

Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   43 bits physical, 48 bits virtual
CPU(s):                          8
On-line CPU(s) list:             0-7
Thread(s) per core:              2
Core(s) per socket:              4
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       AuthenticAMD
CPU family:                      23
Model:                           17
Model name:                      AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx
Stepping:                        0
Frequency boost:                 enabled
CPU MHz:                         1338.250
CPU max MHz:                     2000,0000
CPU min MHz:                     1600,0000
BogoMIPS:                        3992.42
Virtualization:                  AMD-V
L1d cache:                       128 KiB
L1i cache:                       256 KiB
L2 cache:                        2 MiB
L3 cache:                        4 MiB
NUMA node0 CPU(s):               0-7
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Vulnerable
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; Retpolines, IBPB conditional, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
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 mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid ap
                                 erfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext 
                                 perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerp
                                 tr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca

#Error messages:

[    0.869289] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20190816/exoparg2-393)
[    0.869336] 
               Initialized Local Variables for Method [GETP]:
[    0.869337]   Local0: 000000001c28015b <Obj>           Integer 0000000000000003
[    0.869341] Initialized Arguments for Method [GETP]:  (2 arguments defined for method invocation)
[    0.869341]   Arg0:   0000000054561fde <Obj>           Integer 0000000000000005
[    0.869342]   Arg1:   000000006662f2c4 <Obj>           Integer 0000000000000003
[    0.869345] ACPI Error: Aborting method \_TZ.GETP due to previous error (AE_AML_PACKAGE_LIMIT) (20190816/psparse-529)
[    0.869378] ACPI Error: Aborting method \_TZ.CHGZ._CRT due to previous error (AE_AML_PACKAGE_LIMIT) (20190816/psparse-529)
[    0.870179] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20190816/exoparg2-393)
[    0.870227] 
               Initialized Local Variables for Method [GTTP]:
[    0.870227]   Local1: 00000000d18c83fc <Obj>           Integer 0000000000000027
[    0.870229]   Local2: 000000005a121952 <Obj>           Integer 0000000000000027
[    0.870231] Initialized Arguments for Method [GTTP]:  (5 arguments defined for method invocation)
[    0.870231]   Arg0:   0000000012243320 <Obj>           Integer 0000000000000005
[    0.870232]   Arg1:   0000000055615478 <Obj>           Integer 0000000000000006
[    0.870234]   Arg2:   00000000a6916378 <Obj>           Integer 0000000000000010
[    0.870235]   Arg3:   0000000054561fde <Obj>           Integer 0000000000000000
[    0.870237]   Arg4:   000000006662f2c4 <Obj>           Integer 000000000000007F
[    0.870239] ACPI Error: Aborting method \_TZ.GTTP due to previous error (AE_AML_PACKAGE_LIMIT) (20190816/psparse-529)
[    0.870275] ACPI Error: Aborting method \_TZ.CHGZ._TMP due to previous error (AE_AML_PACKAGE_LIMIT) (20190816/psparse-529)
[    0.870328] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20190816/exoparg2-393)

> Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
> kernel version 5.4.0-137 on HP Elitebook 745

Can you please try with an upstream kernel?  Being a distro kernel, it's very possible they're missing some of these patches.

(In reply to Mario Limonciello (AMD) from comment #79)
> > Sorry if I'm posting this wrong, but I get the same error, using Linux Mint
> > kernel version 5.4.0-137 on HP Elitebook 745
> 
> Can you please try with an upstream kernel?  Being a distro kernel, it's
> very possible they're missing some of these patches.

Hi,

Thanks for the suggestion. I tried the upstream 5.4.0-144 and also saw there's a newer version 5.4.0-145, so I tried that one as well, but the issue still persist.

> Thanks for the suggestion. I tried the upstream 5.4.0-144 and also saw
> there's a newer version 5.4.0-145, so I tried that one as well, but the issue
> still persist.

Can you try a newer kernel outside the 5.4 series?  Perhaps the latest LTS kernel, 6.1?

Hello,
I'm still having a similar problem with Kubuntu 23.04 running kernel 6.2.0-20-generic.
This does not prevent the laptop from normally working but I suspect it to play a role in the laptop losing a log of power in sleep mode.
My Laptop: VivoBook_ASUSLaptop X513EAN_K513EA
My processor (if ever this matters): 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
and the error message:
[0.166098] ACPI BIOS Error (bug): Could not resolve symbol (\_SB.PC00.TXHC.RHUB, AE_NOT_FOUND (20210730/dswload2-162))
[0.166110] ACPI Error: AE_NOT_FOUND , During name lookup/catalog (20210730/psobject-220)
[0.166114] ACPI BIOS Error (bug): Could not resolve symbol (\_SB.PC00.TXHC.RHUB.SS01, AE_NOT_FOUND (20210730/dswload2-162))
[0.166117] ACPI Error: AE_NOT_FOUND , During name lookup/catalog (20210730/psobject-220)
[0.166120] ACPI BIOS Error (bug): Could not resolve symbol (\_SB.PC00.TXHC.RHUB.SS02, AE_NOT_FOUND (20210730/dswload2-162))
[0.166123] ACPI Error: AE_NOT_FOUND , During name lookup/catalog (20210730/psobject-220)
[0.166126] ACPI BIOS Error (bug): Could not resolve symbol (\_SB.PC00.TXHC.RHUB.SS03, AE_NOT_FOUND (20210730/dswload2-162))
[0.166129] ACPI Error: AE_NOT_FOUND , During name lookup/catalog (20210730/psobject-220)
[0.166132] ACPI BIOS Error (bug): Could not resolve symbol (\_SB.PC00.TXHC.RHUB.SS04, AE_NOT_FOUND (20210730/dswload2-162))
[0.166134] ACPI Error: AE_NOT_FOUND , During name lookup/catalog (20210730/psobject-220)

Hi, got this again after a Ubuntu update that overwrote my "acpi=off" grub kernel parameter. For anyone that can't boot into the login screen then adding this is the fix.

CPU: Q9650

MB: G41MT-S2PT

BTW the last half of the reports below are after I hit the power button to initiate what would normally be an ACPI shut down. I had to keep the power button held down to force power off.

Cheers.

[
0.333629] ACPI Error: Aborting method _PR.CPU1..
_PDC due to previous error
(AE ALREADY EXISTS) (20221020/psparse-529)
[
0.3336291 ACPI Error: AE_ALREADY_EXISTS, SSDT OxFFFF910E80D15200 Table is a ready loaded (20221020/tbdata-548)
[
0.333629] ACPI Error: Aborting method _PR. CPUZ._PDC due to previous error
(AE _ALREADY _EXISTS) (20221020/psparse-529)
[
0.3336291 ACPI Error: AF
ALREADY_EXISTS, SSDT OxFFFF910E80D14600 Table is a
ready loaded (20221020/tbdata-548)
г
0.3336291 ACPI Error: Aborting method _PR.CPU3..
_PDC due to previous error
(AE_ALREADY _EXISTS) (20221020/psparse-529)

60.8740511 ru: INFO: ru_preempt detected
stalls on CPUs/tasks:
[
60.8743431 rcu: 01-..
1: (0 ticks this GP) idle=4a60/0/0x0 softirq=15/15 fqs
=0 (false positive?)
60.875?361 rcu: rcu_preempt kthread timer wakeup didn't happen for 15001 jif fies! g-1031 f0x0 RU_GP_WAIT_FQS(5) -›state=0x402
[
60.876242] ru: oFossible timer handling issue on cpu-1 timer-softirg-5
г
60.8765361 rcu: rcu_preempt kthread stared for 15002 jiffies g-1031 fOx0 R
CU_GP_WAIT_FQS(5) -›state=0x402 ->cpu=1
[
60.8769991 rcu: Unless ru_preempt kthread gets sufficient CPU time, 00M is now expected behauior.
[
60.8773991 ru: RCU grace-period kthread stack dump:
[
60.8780471 rcu: Stack dump where RCU GP kthread last ran:

Ubuntu 22.04 Jammy Jellyfish (x86-64)
kernel 5.19.0-46-generic

Started seeing this error 7/17/2023

Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632255] ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330)
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632263]
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632263] No Local Variables are initialized for Method [_OSC]
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632264]
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632264] Initialized Arguments for Method [_OSC]:  (4 arguments defined for method invocation)
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632265]   Arg0:   00000000dc18fbcc <Obj>           Buffer(16) 5D A8 3B B2 B7 C8 42 35
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632270]   Arg1:   0000000034c27800 <Obj>           Integer 0000000000000001
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632272]   Arg2:   000000000dc8a41a <Obj>           Integer 0000000000000002
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632273]   Arg3:   00000000653f1daa <Obj>           Buffer(8) 00 00 00 00 05 00 00 00
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632277]
Jul 17 15:45:50 scott-Precision-7670 kernel: [    5.632278] ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

I have this bug about last 7-10 days (probably, I installed a new kernel version) and also random laptop powerdowns (apparently, especially when under load).

ASUSTeK COMPUTER INC.
VivoBook_ASUSLaptop X515EA_X515EA

$ uname -a
Linux victor 5.19.0-40-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 23 21:39:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

As a workaround, I try to use Ubuntu settings of reduced power consumption (instead of Balanced performance that I used to use). After I set this setting, still no crashes, but I am not sure.

Also have this bug. Kernel: 5.15.0.91. Cpu: Intel N3530. Kubuntu 5.27.4. Dual-boot laptop with windows 10. First started seeing this with an earlier Kubuntu version but unfortunately don't know which one, it may have been since 2021 or even earlier.
Also have intermittent power-offs with no warning, but don't know if that's related/relevant.

I'd like to report one more instance of this bug. BUT perhaps more importantly pass on a condition that seems to trigger these ACPI errors at boot time (which you may or may not realize) and which might affect your continued approach to fixing.

I use an old Dell t7400 and just recently decided to activate their TPM (trusted  platform module) in my bios. I had never received any of these boot ACPI errors until I activated the TPM (which uses the broadcom LAN chip for crypto key generation).

Immediately after activation, the ACPI errors unique to my system were reported at boot through dmesg. Upon deactivation AND DISABLING the TPM function (there are 2 distinct steps needed) the boot time ACPI errors cease being reported.

===============
ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU7._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method \_PR.CPU6._PCT due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU6._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330)

and repeated for each core to 0 ......

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

================ my relevant machine info ========

 Kernel: 5.15.0-100-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
    tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Dell product: Precision WorkStation T7400 v: N/A
    serial: <superuser required> Chassis: type: 7 serial: <superuser required>
  Mobo: Dell model: 0RW199 serial: <superuser required> BIOS: Dell v: A11 date: 04/30/2012
CPU:
  Info: 2x 4-core model: Intel Xeon E5450 bits: 64 type: MCP SMP smt: <unsupported>
    arch: Core Yorkfield rev: A cache: L1: 2x 256 KiB (512 KiB) L2: 2x 12 MiB (24 MiB)
  Speed (MHz): avg: 2693 high: 3591 min/max: 2000/3000 cores: 1: 3591 2: 2394 3: 2394 4: 2394
    5: 3591 6: 2394 7: 2394 8: 2394 bogomips: 57457
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx

Network:
  Device-1: Broadcom NetXtreme BCM5754 Gigabit Ethernet PCI Express vendor: Dell driver: tg3
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 08:00.0 chip-ID: 14e4:167a
    class-ID: 0200
=====
I hope this is useful information.

I consider this problem serious, I have 2 hard drives that are lost. This error over time only increases the number of lines with this problem, until finally Busybox appears asking to build the shell, where as a lay Linux supporter I don't know what to do! I have 3 machines with Linux, and this appears on all of them from the moment they are installed.
I would like to know a solution to solve this and not lose each installed disk! Is there a way to resolve this? APT UPDATE doesn't work!

Is this a Mint problem?? Why do I only have this distribution? Does it also occur in Unbutu or elsewhere?

Sorry for using Google Translater!