ACPI errors ar boot

kitman · February 11, 2019, 7:44am

Hi,
I have installed 15.0 on my ASUS Z370-G + Intel i7 8700 box that had run 42.3 without issue.

chris@asus-roc:~> uname -a
Linux asus-roc 4.12.14-lp150.12.45-default #1 SMP Mon Jan 14 20:29:59 UTC 2019 (7a62739) x86_64 x86_64 x86_64 GNU/Linux

I notice now I get a lot of ACPI related errors on screen at boot time -

2019-02-11T11:02:27.153189+08:00 asus-roc kernel:     0.136195] ACPI: Added _OSI(Processor Device)
2019-02-11T11:02:27.153191+08:00 asus-roc kernel:     0.136195] ACPI: Added _OSI(3.0 _SCP Extensions)
2019-02-11T11:02:27.153191+08:00 asus-roc systemd[1]: Started Watch for changes in CA certificates.
2019-02-11T11:02:27.153192+08:00 asus-roc kernel:     0.136195] ACPI: Added _OSI(Processor Aggregator Device)
2019-02-11T11:02:27.153194+08:00 asus-roc systemd[1]: Reached target Paths.
2019-02-11T11:02:27.153196+08:00 asus-roc kernel:     0.137312] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170303/dswload2-191)
2019-02-11T11:02:27.153197+08:00 asus-roc kernel:     0.137319] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170303/psobject-241)
2019-02-11T11:02:27.153197+08:00 asus-roc systemd[1]: Reached target Basic System.
2019-02-11T11:02:27.153198+08:00 asus-roc kernel:     0.137322] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX] (Node ffff880187d5bb68), AE_NOT_FOUND (20170303/psparse-543)
2019-02-11T11:02:27.153200+08:00 asus-roc kernel:     0.137693] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170303/dswload2-191)
2019-02-11T11:02:27.153201+08:00 asus-roc kernel:     0.137696] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170303/psobject-241)
2019-02-11T11:02:27.153200+08:00 asus-roc systemd[1]: Starting Name Service Cache Daemon...
2019-02-11T11:02:27.153204+08:00 asus-roc systemd[1]: Starting NTP client/server...
2019-02-11T11:02:27.153203+08:00 asus-roc kernel:     0.137698] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX] (Node ffff880187d57988), AE_NOT_FOUND (20170303/psparse-543)
2019-02-11T11:02:27.153207+08:00 asus-roc kernel:     0.140287] ACPI: Executed 53 blocks of module-level executable AML code
2019-02-11T11:02:27.153207+08:00 asus-roc systemd[1]: Started Detect if the system suffers from bsc#1089761.
2019-02-11T11:02:27.153208+08:00 asus-roc kernel:     0.152218] ACPI: Dynamic OEM Table Load:
2019-02-11T11:02:27.153210+08:00 asus-roc kernel:     0.152226] ACPI: SSDT 0xFFFF880185EE7000 0006D5 (v02 PmRef  Cpu0Ist  00003000 INTL 20160422)
2019-02-11T11:02:27.153211+08:00 asus-roc kernel:     0.152226] ACPI: Executed 1 blocks of module-level executable AML code
2019-02-11T11:02:27.153211+08:00 asus-roc kernel:     0.152251] ACPI: \_PR_.PR00: _OSC native thermal LVT Acked
2019-02-11T11:02:27.153210+08:00 asus-roc systemd[1]: Starting Modem Manager...
2019-02-11T11:02:27.153213+08:00 asus-roc kernel:     0.153450] ACPI: Dynamic OEM Table Load:
2019-02-11T11:02:27.153215+08:00 asus-roc systemd[1]: Starting Update cron periods from /etc/sysconfig/btrfsmaintenance...
2019-02-11T11:02:27.153215+08:00 asus-roc kernel:     0.153454] ACPI: SSDT 0xFFFF880426544800 0003FF (v02 PmRef  Cpu0Cst  00003001 INTL 20160422)
2019-02-11T11:02:27.153217+08:00 asus-roc kernel:     0.153609] ACPI: Executed 1 blocks of module-level executable AML code
2019-02-11T11:02:27.153218+08:00 asus-roc kernel:     0.153757] ACPI: Dynamic OEM Table Load:

A bit of googling found me this article about a line to ‘/etc/rc.local’.

Is this technique valid for Leap 15.0? If not, how do I resolve it?
How come I get these messages now after 42.3?

Thanks,
Chris.

OrsoBruno · February 11, 2019, 4:01pm

Hi, apparently (some) ASUS firmwares are not as compliant to the ACPI specification and ACPI code in newer kernels is far more picky than it used to be, so now you see stuff that just went unnoticed with Leap 42.3.
Apparently you just get a few error lines at boot, not the constant flow of interrupts mentioned in the article you referred to; if that is the case, I would just ignore the few error lines and be happy with that.
IMHO the “solution” mentioned in the article does not directly apply to your case; maybe an ACPI expert might suggest something similar, but I would not fiddle with ACPI code unless I don’t know exactly what I’m doing.

arvidjaar · February 11, 2019, 7:32pm

This sounds very similar. You may consider testing kernel from kernel:HEAD; if errors go away, open bug report on openSUSE bugzilla.

kitman · February 12, 2019, 12:10pm

Out of interest I upgraded my MB’s firmware today to version 1802 that was released last month. It made no difference. But I don’t get a flood of ACPI error messages in /var/log/messages so it’s not really fatal - just frightening when first seeing those few messages at boot

Plus I’m a bit too wary of trying a different kernel so I will close this one.

Thanks for your replies.
Chris.

nrickert · February 12, 2019, 2:22pm

It’s more work for you to install and occasionally update. But, apart from that, there should not be any concerns. The kernel is still prepared by the openSUSE team and should work with your system.