I recently switched from Windows 10 to Ubuntu. So far so good, but I get these errors on every boot. I was not getting these when on Windows 10 (not sure if it is because Windows didn't have these errors or Windows just hided them from me) I just ignored them since the system can still boot and I think these are not fatal errors.
But now I actually want to know if I should take action, or this can be safely ignored (i.e does not do any harm), or should I add noacpi or something? I read that might also stop other working acpi thingies from working so I just ignored until this day I decided to ask here.
The reason I actually want to know this can be solved without any harm is, well, it is annoying to see these every boot and they seem to delay boot a bit (not sure if it is because of it though, but it hangs for like 1.5-2 seconds waiting on blinking _ after the error before going to ubuntu).
The errors are these:
ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_NOT_FOUND) (20201113/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._PPC], AE_NOT_FOUND (20201113/psargs-330)I don't know what PR or PPC means but from the CPU0 part, it seems like something related to my CPU's first core (I have a dual core one) but my CPU is working fine (and was working fine in Windows too)
1 Answer
Some BIOS/UEFI developers are just lazy and don't implement the entire ACPI specification into their BIOS/UEFI, or more worse, they implement it in the wrong way. When Linux tries to read some specific ACPI parameters, which don't exist, or are wrong, it fails and reports this kind of error.
You may try a BIOS/UEFI update, but in most times you may just ignore these kind of "errors" and treat them more like a warning.
I'll give you an example how this might happen.
Mainboard-manufacturer XYZ creates 2 similar mainboards, but one has an additional Ethernet adapter.
Mainboard-manufacturer XYZ creates a BIOS/UEFI for the mainboard with the additional Ethernet adapter and installs it on the mainboard with the additional Ethernet adapter.
Mainboard-manufacturer XYZ is lazy and uses the same BIOS/UEFI image for the mainboard without the additional Ethernet adapter.
Some user named Mustafa Öncel installs Linux on a mainboard of XYZ which hasn't the additional Ethernet adapter. Linux kernel reads the ACPI-table of the BIOS/UEFI, this table says there is an additional Ethernet adapter, Linux tries to read the memory area, but fails, because there is no additional Ethernet adapter.
.
PS if this error didn't occurred in the past, but now it does, it may be because you use a new Linux kernel, you changed your BIOS/UEFI or your hardware fails.
1
