Linux Developer Systems

Last reply by 09-07-2018 Unsolved
Start a Discussion
2 Bronze
2 Bronze

Dell XPS 15 / Precision 5510 Linux ACP errors


We are currently running Dell Precision and Dell XPS 15 systems in our environment, and at boot and when waking from sleep the kernel log gets hogged with ACPI errors;

ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff9e441d123488), AE_NOT_FOUND (20160930/psparse-543)

ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff9e441d123488), AE_NOT_FOUND (20160930/psparse-543)


This happens on both models, the XPS 15 aswell as the Precision 5510. We have tried to flash older BIOS versions aswell as the latest BIOS version but they make no difference.

There is a Bugzilla report; . There is stated that this is a BIOS bug;

"SB_.PCI0.LPCB.H_EC.ECAV should not be defined in any dynamic SSDT tables. So this is a BIOS bug to me. Closed." 

Did we configure something wrong or are we overlooking something? Is this something that Dell should fix? If i search for Google on this bug multiple people seem to be affected by this bug...

Thanks in advance.

Replies (4)
2 Bronze
2 Bronze

I am also affected by this bug on an XPS 9550 with Ubuntu 16.04.2 kernel 4.8.0-46-generic.

On suspend/resume I also get the following error:

[127816.369668] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup failure, AE_NOT_FOUND (20160422/psargs-359)

[127816.369701] ACPI Error: Method parse/execution failed [\PNOT] (Node ffff92b86d0e0b68), AE_NOT_FOUND (20160422/psparse-542)

[127816.369737] ACPI Error: Method parse/execution failed [\_SB.AC._PSR] (Node ffff92b86d0f3988), AE_NOT_FOUND (20160422/psparse-542)

[127816.369747] ACPI Exception: AE_NOT_FOUND, Error reading AC Adapter state (20160422/ac-128)

2 Bronze
2 Bronze

This behaviour causes issues with kernel 4.10.10 and onwards. The kernel team has commited a new patch set ( ) this causes the LID always reported to be open even when the laptops are docked. Due the kernel unable being to read the ACPI LID status it always assumes its open even though its closed.

Could someone at Dell please look into this?

3 Silver

For reference I reported same thing some time ago (3.3.2017) without any response from Dell. You can take a look at This is definitely not funny and I hope someone will notice it or at worst case tells us where should this be reported.

Your original report seems to be restricted now :Hmm:

Top Contributor
Latest Solutions