Bug 1524599

Summary: ACPI Exceptions after upgrading to 4.14
Product: [Fedora] Fedora Reporter: Alexander Ploumistos <alex.ploumistos>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: airlied, ajax, bskeggs, ewk, hdegoede, ichavero, info, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, jorgeml, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-15 07:48:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output during boot none

Description Alexander Ploumistos 2017-12-11 17:34:21 UTC
Created attachment 1366221 [details]
dmesg output during boot

Description of problem:

After installing kernel 4.14, I started getting these messages during boot:

[    0.033846] ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
[    0.033846] ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
[    0.033846] ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
[    0.033846] ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)



Version-Release number of selected component (if applicable):

kernel-4.14.3-300.fc27.x86_64



Additional info:

This is on a Gigabyte GA-MA790FXT-UD5P motherboard with an AMD Phenom II X6 1100T CPU. I haven't seen any similar messages on any other system running the 4.14 kernel.

So far, Google returns just a couple of results and one of them is also about a Gigabyte motherboard (GA-880GMA-UD2H) with a Phenom II X4 840.

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

Comment 1 Jorge Martínez López 2017-12-13 11:11:15 UTC
Same thing here:

ACPI: Added _OSI(Processor Aggregator Device)
ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)

My motherboard is also a Gigabyte (GA-890GPA-UD3H) with an AMD Phenom II X6 1055T processor.

Comment 2 Hans de Goede 2017-12-14 12:21:33 UTC
Hi,

Can one of you please file an upstream bug for this here:

https://bugzilla.kernel.org/enter_bug.cgi?product=ACPI

You will need to create an account there (just requires an email-address, not a huge form to fill).

As component just pick "ACPICA-core"

Thanks & Regards,

Hans

Comment 3 Jorge Martínez López 2017-12-14 20:32:09 UTC
Thanks Hans!

I have submitted a bug there: https://bugzilla.kernel.org/show_bug.cgi?id=198167

Comment 4 Hans de Goede 2017-12-15 07:48:51 UTC
(In reply to Jorge Martínez López from comment #3)
> Thanks Hans!
> 
> I have submitted a bug there:
> https://bugzilla.kernel.org/show_bug.cgi?id=198167

Thank you. I don't expect anything to be done about this at the Fedora level (other then hopefully picking up the fix eventually) so I'm going to close this bug with the resolution being this being handled / tracked upstream.

Comment 5 Hans de Goede 2018-01-12 11:46:55 UTC
Since this wasn't getting anywhere upstream and I managed to reproduce this on one of my laptops I've gotten involved and written a patch-set lowering these new errors log-level to warning so that they will not show on the console.

Hopefully this patch-set will be accepted upstream.

Comment 6 infove 2018-04-29 15:29:10 UTC
The linked kernel.org but has been marked closed/fixed and patches issued. Can you _please_ incorporate these patches into Fedora kernels (and no, not just the most recent one for 28 beta!!!)

This issue is annoying thousands of Fedora users worldwide, your prompt cooperation will sure be much appreciated.

Comment 7 infove 2018-04-29 15:29:40 UTC
The linked kernel.org bug has been marked closed/fixed and patches issued. Can you _please_ incorporate these patches into Fedora kernels (and no, not just the most recent one for 28 beta!!!)

This issue is annoying thousands of Fedora users worldwide, your prompt cooperation will sure be much appreciated.