Ask Your Question

Revision history [back]

I'll second the notion that firmware writers do not always create correct ACPI tables -- and the PCCT has had some changes to it very recently. What the messages say is that the ACPI tables have some incorrect content; without looking at the tables in detail, I'm guessing that at least the PCCT, and possibly the DSDT (or some SSDT) tables have a few entries that should really be cleaned up. I collect this kind of goofiness, by the way, so I'd love to have a copy of everything in /sys/firmware/acpi/tables, if you have a chance; it helps with my work on the ACPI standards committee.

The entries you have shown are probably harmless. In general, if there are ACPI errors, that means the kernel does not know how to find some bit of hardware and make it start up. And, in general, the kernel sets up reasonable defaults when there are errors. The PCC subspace error, for example, means that the kernel cannot communicate with firmware about something (it's used in several places) properly. If it is the PCC subspace used for adjusting CPU frequency (one of the possibilities -- we don't know from the messages alone), it might mean that the CPU always runs at the fastest possible speed. That's not necessarily a problem, though, even on a laptop where it might use more battery, because the firmware may take care of adjusting CPU frequency independently. You might never notice.

The first line shown is the PCC subspace problem; at least one of the subspaces could not be set up. The last three lines are probably part of a single error in the DSDT where CPU power adjustment capabilities are described, and ACPI does not understand the description. Again, the kernel default will be to just run at full power and let firmware adjust it if it can.

I would definitely complain to the hardware vendor about this. Any time there is an ACPI error, the hardware is not working at its best. It will work, and work reasonably well, but may not be able to take advantage of all the cool features the vendor has built in. If the vendor is responsive, they'll already have a firmware update available. If they are not, then filing a bug with them could help.