On Mon, Dec 8, 2014 at 4:21 PM, Rafael J. Wysocki <rafael@xxxxxxxxxx> wrote:
>
> Also the ACPI core is now going to support the _DEP configuration
> information in a limited way.
Hmm. That seems to be the cause of this annoying new message:
...
ACPI: Using IOAPIC for interrupt routing
PCI: Using host bridge windows from ACPI; if necessary, use
"pci=nocrs" and report a bug
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:00: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:01: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:02: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:03: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:04: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:05: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:06: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb200)
acpi LNXCPU:07: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb840)
acpi device:27: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb840)
acpi device:3f: Failed to evaluate _DEP.
ACPI: [Package] has zero elements (ffff88040ccdb8c0)
acpi LNXVIDEO:00: Failed to evaluate _DEP.
ACPI: Power Resource [FN00] (off)
...
which doesn't seem to hinder anything from working, but is extremely
annoying because it's printed out as some super-important "KERN_ERR
message of Doom!"
I don't see why incomplete ACPI tables would *ever* be "KERN_ERR"
level messages, but I particularly don't see it when it seems to be
our own meaningless fake entries.
Linus
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
