Re: [kernel 3.13.0-06058-g2d08cd0] Strange ACPI error messages

From: Rafael J. Wysocki
Date: Sat Jan 25 2014 - 17:14:57 EST


On Saturday, January 25, 2014 05:32:19 PM JÃrg Otte wrote:
> 2014-01-25 Rafael J. Wysocki <rjw@xxxxxxxxxxxxx>:
> > On Saturday, January 25, 2014 11:03:09 AM JÃrg Otte wrote:
> >> Kernel 3.13.0-06058-g2d08cd0 displays following errors on the console:
> >>
> >> ACPI: \_PR_.CPU4: failed to get CPU APIC ID.
> >> ACPI: \_PR_.CPU5: failed to get CPU APIC ID.
> >> ACPI: \_PR_.CPU6: failed to get CPU APIC ID.
> >> ACPI: \_PR_.CPU7: failed to get CPU APIC ID.
> >>
> >> I don't have CPUs 4..7! Error messages regarding not existing
> >> CPUs should not be displayed.
> >> kernel 3.13.0-05617-g3aacd62 and before did'nt show this messages.
> >>
> >> This is a regression. I never saw this messages before.
> >
> > Does your system show any other suspicious symptoms or are you worried about
> > those messages only?
> >
> > Rafael
> >
>
> what's looking badly is this:
>
> ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_]
> (20131218/hwxface-580)
> ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_]
> (20131218/hwxface-580)

That means your BIOS doesn't support system sleep states S1 and S2, but we
should be able to suppress those messages I think.

> and this:
>
> acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
> \_SB_.PCI0:_OSC invalid UUID
> _OSC request data:1 1e 0
> acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

That means the BIOS doesn't want to grant the kernel control of extended
PCIe features on your system.

> but these messages are not new.

They indicate things that are not supported by the BIOS, but I agree that the
messages are a bit cryptic.

Thanks!

--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/