ACPI Errors when booting on 4.9 Kernel

Since I am on 4,9. I have been getting these errors when I boot. They seem harmless, but I would kust like to make sure:


Dec 28 22:26:46 linux-azyr kernel: **ACPI**: Sleep Button [SLPB]
Dec 28 22:26:46 linux-azyr kernel: **ACPI**: Power Button [PWRB]
Dec 28 22:26:46 linux-azyr kernel: **ACPI**: Lid Switch [LID0]
Dec 28 22:26:46 linux-azyr kernel: **ACPI**: Power Button [PWRF]
Dec 28 22:26:46 linux-azyr kernel: **ACPI**: bus type USB registered
Dec 28 22:26:46 linux-azyr kernel: **ACPI**: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: \_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: Method parse/execution failed \_TZ.FN00._ON] (Node ffff96bc7fd02eb0), AE_NOT_FOUND (20160831/psparse-543)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: \_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: Method parse/execution failed \_TZ.FN00._ON] (Node ffff96bc7fd02eb0), AE_NOT_FOUND (20160831/psparse-543)
Dec 28 22:26:48 linux-azyr kernel: **ACPI**: AC Adapter [ADP1] (on-line)
Dec 28 22:26:48 linux-azyr kernel: **ACPI**: Battery Slot [BAT0] (battery present)
Dec 28 22:26:48 linux-azyr kernel: **ACPI**: Thermal Zone [THM] (70 C)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: \_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: Method parse/execution failed \_TZ.TZ00._TMP] (Node ffff96bc7fd02000), AE_NOT_FOUND (20160831/psparse-543)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: \_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: Method parse/execution failed \_TZ.TZ00._TMP] (Node ffff96bc7fd02000), AE_NOT_FOUND (20160831/psparse-543)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: \_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: Method parse/execution failed \_TZ.TZ01._TMP] (Node ffff96bc7fd02c08), AE_NOT_FOUND (20160831/psparse-543)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: \_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Dec 28 22:26:48 linux-azyr kernel: **ACPI** Error: Method parse/execution failed \_TZ.TZ01._TMP] (Node ffff96bc7fd02c08), AE_NOT_FOUND (20160831/psparse-543)

After looking at the logs, it appears I have been getting this error for a while, they were just not displayed.

Hi
Is the system BIOS up to date? Similar to this (closed won’t fix) bug;
https://bugzilla.kernel.org/show_bug.cgi?id=43229

I have the latest BIOS from Dell. I am frankly quite ignorant of ACPI, but the errors look different to me.

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
82 structures occupying 4691 bytes.
Table at 0x000E5070.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: Dell Inc.
        Version: A09
        Release Date: 05/13/2016
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 6144 kB
        Characteristics:
                PCI is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                EDD is supported
                Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
                Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
                5.25"/360 kB floppy services are supported (int 13h)
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 kB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                8042 keyboard services are supported (int 9h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                BIOS boot specification is supported
                Targeted content distribution is supported
                UEFI is supported
        BIOS Revision: 65.9

Hi
What type of DELL system? It’s the acpi DSDT table, if everything is working (Fn keys for vol, wifi, brightness, lid switch etc), you should be fine… You could perhaps look at raising a kernel bug, but think they will advise to talk to the DELL folks…

FWIW, I have a DELL Inspiron 5555 with A12 firmware rev 65.12 and don’t see any acpi errors.

All the function keys etc. seem to be working. So should I suppress those events in the log?

On Thu 29 Dec 2016 02:26:02 PM CST, Thiudans wrote:

malcolmlewis;2805913 Wrote:
> Hi
> What type of DELL system? It’s the acpi DSDT table, if everything is
> working (Fn keys for vol, wifi, brightness, lid switch etc), you
> should be fine… You could perhaps look at raising a kernel bug, but
> think they will advise to talk to the DELL folks…
>
> FWIW, I have a DELL Inspiron 5555 with A12 firmware rev 65.12 and
> don’t see any acpi errors.

All the function keys etc. seem to be working. So should I suppress
those events in the log?

Hi
Perhaps you could as long as everything is working as expected, just
keep an eye out for a BIOS update, if it starts playing up with later
kernels you might need to re-enable…


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.36-41-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

This is the relevant section of dmesg with a Acer Aspire V



    0.542495] ACPI: Added _OSI(Module Device)
    0.542496] ACPI: Added _OSI(Processor Device)
    0.542497] ACPI: Added _OSI(3.0 _SCP Extensions)
    0.542498] ACPI: Added _OSI(Processor Aggregator Device)
    0.542818] ACPI: Executed 1 blocks of module-level executable AML code
    0.549578] ACPI Error: No handler for Region [RAM_] (ffff97305a8cf120) [EmbeddedControl] (20160831/evregion-166)
    0.549587] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160831/exfldio-299)
    0.549596] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC0._REG] (Node ffff97305a8d0a78), AE_NOT_EXIST (20160831/psparse-543)                                                                                                           
    0.549682] ACPI Error: No handler for Region [RAM_] (ffff97305a8cf120) [EmbeddedControl] (20160831/evregion-166)
    0.549687] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160831/exfldio-299)
    0.549693] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC0._REG] (Node ffff97305a8d0a78), AE_NOT_EXIST (20160831/psparse-543)     


It also appeared with the arrival of the 4.9 kernel.

I’ve got no idea if there is a real problem or not (so, “not”, then…) but it’s not only Dell.

I get similiar entries since up-dating to 4.9.

Ditto… Same here.

After looking at the logs, it appears I have been getting this error for a while, they were just not displayed.

Exactly, so the ACPI errors have always been there, 4.9 just seems to do a “better”(?) job in displaying them on startup.

Such warnings/errors are pretty common and as long as you don’t experience any serious problems, just ignore them.

Although being a standard, ACPI is the one often being ignored (on purpose?) by some (many, most?) vendors, just think of those funny kernel paramters sometimes needed to “trick” the BIOS so it “thinks” you are running some Windows OS in order to get access to functions otherwise being blocked.

As GKH once said “ACPI code is nasty”.

AK

True, but enabling new errors LOOKS like a kernel issue/ACPI/whatever issue.

This feels like a pretty sweeping statement. I’m not sure I’ve ever seen ACPI errors before. It would seem that some work went into fixing ACPI errors for 4.9

see:

https://lwn.net/Articles/705010/

which at first sight is inconsistent with “just ignore [errors]”

and then there is

https://lkml.org/lkml/2016/10/5/341

> Are those failures so bad that they should be marked as errors?

They come from ACPICA that appears to have problems with some AML in
the ACPI tables, but I agree that they should rather be debug
messages.

AK