Page 1 of 1

ACPI BIOS Error

PostPosted: Sep 1st, '22, 21:37
by dfgrbac
This Mageia boot error has been happening for about a month now. I am working on a new problem with k3b creating a DVD, but I have no idea if this is connected. See the following:

Code: Select all
[root@localhost ~]# journalctl -ab
...
Sep 01 11:16:33 localhost kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (2021073>
Sep 01 11:16:33 localhost kernel: ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (202107>
Sep 01 11:16:33 localhost kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (2021073>
Sep 01 11:16:33 localhost kernel: ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (202107>
Sep 01 11:16:33 localhost kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (2021073>
Sep 01 11:16:33 localhost kernel: ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (202107>


Searching for an answer, I came to kernel.org and found this article. It says in part:
Upgrading ACPI tables via initrd https://www.kernel.org/doc/html/latest/admin-guide/acpi/initrd_table_override.html
...
"Complain to your platform/BIOS vendor if you find a bug which is so severe that a workaround is not accepted in the Linux kernel. And this facility allows you to upgrade the buggy tables before your platform/BIOS vendor releases an upgraded BIOS binary.

This facility can be used by platform/BIOS vendors to provide a Linux compatible environment without modifying the underlying platform firmware."

I don't understand any of this, but I hope you can clear up the messages.

added code tags ~Germ

Re: ACPI BIOS Error

PostPosted: Sep 1st, '22, 22:10
by sturmvogel
You have a buggy BIOS with broken ACPI tables. Newer kernels don't suppress this irrelevant messages from your BIOS.
Kernel guys are working on a solution to suppress this messages...
https://bugzilla.kernel.org/show_bug.cgi?id=213023

This is not a Mageia or linux bug. It is caused by the vendor of your motherboard/BIOS.