FS#57372 - [linux] ACPI Exceptions after upgrading to 4.15

Attached to Project: Arch Linux
Opened by mozzi (Mozzi) - Sunday, 04 February 2018, 18:46 GMT
Last edited by Toolybird (Toolybird) - Thursday, 18 August 2022, 22:14 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

dmesg output during boot

Description of problem:


After installing kernel 4.15, I started getting these messages during boot (Seems to be in :



[ 0.183357] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.183385] ACPI: Added _OSI(Module Device)
[ 0.183386] ACPI: Added _OSI(Processor Device)
[ 0.183386] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.183387] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.184590] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.184603] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.184612] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.184621] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.184663] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.184672] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.184681] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.184691] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.184732] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.184741] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.184749] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.184758] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.184800] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.184809] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.184819] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.184828] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.184869] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.184879] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.184889] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.184898] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.184939] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.184948] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.184958] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.184967] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.185010] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.185019] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.185028] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.185037] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.185079] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.185089] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.185098] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.185107] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.185148] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.185157] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.185166] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.185176] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.185217] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[ 0.185227] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
[ 0.185236] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[ 0.185245] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[ 0.186958] ACPI: Interpreter enabled
[ 0.186976] ACPI: (supports S0 S3 S4 S5)
[ 0.186978] ACPI: Using IOAPIC for interrupt routing

Additional info:

This is on a Gigabyte GA-78LMT-USB3 6.0 motherboard with an AMD® Fx(tm)-4300 quad-core processor × 4 CPU. I have already seen any similar messages with the 4.14 kernel.

Other than these messages, I haven't encountered any "actual" problems yet.
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 18 August 2022, 22:14 GMT
Reason for closing:  Upstream
Comment by mattia (nTia89) - Sunday, 27 February 2022, 13:19 GMT
I cannot reproduce the issue. Is it still valid?
Comment by Toolybird (Toolybird) - Thursday, 18 August 2022, 22:13 GMT
This is due to buggy vendor BIOS firmware. I have an old Gigabyte system somewhere that displays same. Many examples online e.g. [1]. It's just warnings and definitely harmless.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=198167

Loading...