Home / ubuntu / Questions / 1416198
In Process
Gary Wright
Asked: 2022-06-28 23:56:05 +0800 CST

Ubuntu 22.04 "ACPI BIOS Error (bug): Could not resolve symbol" errors on Asus X705UA

  • 772

Running Ubuntu 22.04, Kernel 5.15.0-40-generic x86_64 Since the last kernel update about 3 weeks ago, I have started to get the following errors:-

I have updated the ASUS laptop with the latest BIOS version V322 - but this has done nothing.

ACPI errors shown here...
[    0.341051] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[    0.341075] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.341153] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[    0.341171] ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.341250] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[    0.341268] ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    0.342812] ACPI: thermal: Thermal Zone [THRM] (34 C)
asus

2 Answers

  1. This is a known bug in certain versions of the Linux kernel (5.12.x and 5.17.2+, among others) with Collaborative Processor Performance Control (CPPC) affecting Intel CPUs. The kernel guys are working on a patch:

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

    • 6

  2. To get rid of these messages while booting, you can add loglevel=3 to GRUB_CMDLINE_LINUX_DEFAULT in etc/default/grub, so that it will look like this:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash loglevel=3"

    then update grub using command: sudo update-grub

    Note that, adding 'loglevel=3' simply disables the non-critical error but doesn't resolve it. Since this is an active issue reported on bugzilla and has been resolved for 5.18.xx kernels, you can try upgrading your linux kernel to this version using software and updates. Hopefully, it could be resolved soon for 5.15.XX and other kernels. To get more info on why this happens @LordBoltar has explained very well in this thread.

    • 2