Bug 207837 - Dell Vostro 3491 fw 1.9.1 ACPI errors
Summary: Dell Vostro 3491 fw 1.9.1 ACPI errors
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Erik Kaneda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-21 21:59 UTC by James Ettle
Modified: 2020-08-18 01:45 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.6.13
Subsystem:
Regression: No
Bisected commit-id:


Attachments
acpidump for Vostro 3491 (1.58 MB, text/plain)
2020-06-22 13:45 UTC, James Ettle
Details
updated acpidump from latest firmware (1.58 MB, text/plain)
2020-06-23 23:17 UTC, James Ettle
Details

Description James Ettle 2020-05-21 21:59:22 UTC
This is a Dell Vostro 3491 notebook running the latest UEFI firmware. The following ACPI-related error messages appear shortly after logging into my desktop environment:


[   54.771734] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00000003D) is beyond end of object (length 0x10) (20200110/exoparg2-393)
[   54.771752] ACPI Error: Aborting method \_SB.GINF due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.771756] ACPI Error: Aborting method \_SB.GADR due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.771759] ACPI Error: Aborting method \_SB.SGOV due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.771762] ACPI Error: Aborting method \_SB.CGWR due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.771764] ACPI Error: Aborting method \_SB.TBFP due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.771768] ACPI Error: Aborting method \_SB.WMTF.WMTF due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.776046] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00000003D) is beyond end of object (length 0x10) (20200110/exoparg2-393)
[   54.776062] ACPI Error: Aborting method \_SB.GINF due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.776066] ACPI Error: Aborting method \_SB.GADR due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.776069] ACPI Error: Aborting method \_SB.SGOV due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.776072] ACPI Error: Aborting method \_SB.CGWR due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.776075] ACPI Error: Aborting method \_SB.TBFP due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)
[   54.776079] ACPI Error: Aborting method \_SB.WMTF.WMTF due to previous error (AE_AML_PACKAGE_LIMIT) (20200110/psparse-529)


There are no obvious adverse effects. Seen on the current Fedora kernel kernel-5.6.13-300.fc32.x86_64, but also present when I tried long-term 5.4 and 4.19 kernels.

Another one I've seen is the following:


[ 7769.786461] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20200110/psargs-330)
[ 7769.786472] ACPI Error: Aborting method \_TZ.FNCL due to previous error (AE_NOT_FOUND) (20200110/psparse-529)
[ 7769.786482] ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20200110/psparse-529)


which seems related to fan control. I saw it when I tried 

echo 1 > /sys/class/thermal/cooling_device0/cur_state

(The fan seems to be otherwise firmware controlled anyway.)

Obviously these may very well be legit firmware bugs, but I'd rather run it past the experts before I take it to Dell. Let me know what table dumps etc. will be required.
Comment 1 Zhang Rui 2020-06-22 13:42:47 UTC
Please attach the full acpidump output.
say, "./acpidump > acpidump.out"
Comment 2 James Ettle 2020-06-22 13:45:57 UTC
Created attachment 289789 [details]
acpidump for Vostro 3491

acpidump, as requested
Comment 3 James Ettle 2020-06-23 23:17:42 UTC
Created attachment 289853 [details]
updated acpidump from latest firmware

Got BIOS 1.9.1 update today, still get the same error messages. acpidump from firmware 1.9.1 attached.
Comment 4 James Ettle 2020-08-17 16:06:04 UTC
This seems to be fixed with kernel 5.7.14 and BIOS 1.10.1.

Note You need to log in before you can comment on or make changes to this bug.