ACPI Errors in dmesg after Migration to kernel-3.10.0-1127.10.1.el7.x86_64 for Centos 7.8

General support questions
Post Reply
zahn-martin
Posts: 35
Joined: 2020/05/05 19:44:15

ACPI Errors in dmesg after Migration to kernel-3.10.0-1127.10.1.el7.x86_64 for Centos 7.8

Post by zahn-martin » 2020/06/24 10:44:57

I migrated to the last kernel for centos 7.8: kernel-3.10.0-1127.10.1.el7.x86_64
and now I get ACPI Errors as follows:

dmesg | grep Error

[ 0.017140] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20130517/dswload-194)
[ 0.087461] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359)
[ 0.087464] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff92396eeefc60), AE_NOT_FOUND (20130517/psparse-536)

I googled a lot and found no real solution, perhaps BIOS

The system is working correctly !

Can you help me with these ACPI Error ?

tunk
Posts: 1205
Joined: 2017/02/22 15:08:17

Re: ACPI Errors in dmesg after Migration to kernel-3.10.0-1127.10.1.el7.x86_64 for Centos 7.8

Post by tunk » 2020/06/24 11:01:25

kernel-3.10.0-1127.13.1 was released yesterday, maybe that works better?

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: ACPI Errors in dmesg after Migration to kernel-3.10.0-1127.10.1.el7.x86_64 for Centos 7.8

Post by TrevorH » 2020/06/24 11:14:00

Do they affect anything? I'd guess no. In which case, just ignore them.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

zahn-martin
Posts: 35
Joined: 2020/05/05 19:44:15

Re: ACPI Errors in dmesg after Migration to kernel-3.10.0-1127.10.1.el7.x86_64 for Centos 7.8

Post by zahn-martin » 2020/06/24 12:18:49

Thank you for your answer !

I changed to the newest kernel: kernel-3.10.0-1127.13.1.el7.x86_64 - same thing.

But i noticed, that the ACPI Error only encounter on ONE specific hardware, on the other Hardware no Errors.

So my conclusion: It must be the BIOS or/and the specific hardware. I leave it as it is, because no other services are affected.

Thanks Martin Zahn

Post Reply