Created attachment 293291 [details] Output of `acpidump` Linux 5.10-rc1+ prints the messages below: ``` […] [ 4.281045] ACPI BIOS Error (bug): Could not resolve symbol [\S1CC], AE_NOT_FOUND [ 4.281132] ACPI BIOS Error (bug): Could not resolve symbol [\S1HP], AE_NOT_FOUND (20200925/psargs-330) [ 4.281287] ACPI BIOS Error (bug): Could not resolve symbol [\S1PV], AE_NOT_FOUND (20200925/psargs-330) [ 4.281408] ACPI BIOS Error (bug): Could not resolve symbol [\S1AC], AE_NOT_FOUND (20200925/psargs-330) [ 4.285921] ACPI BIOS Error (bug): Could not resolve symbol [\S2CC], AE_NOT_FOUND (20200925/psargs-330) [ 4.285956] ACPI BIOS Error (bug): Could not resolve symbol [\S2HP], AE_NOT_FOUND (20200925/psargs-330) [ 4.285988] ACPI BIOS Error (bug): Could not resolve symbol [\S2PV], AE_NOT_FOUND (20200925/psargs-330) [ 4.291921] ACPI BIOS Error (bug): Could not resolve symbol [\S3CC], AE_NOT_FOUND (20200925/psargs-330) [ 4.291971] ACPI BIOS Error (bug): Could not resolve symbol [\S3HP], AE_NOT_FOUND (20200925/psargs-330) [ 4.292014] ACPI BIOS Error (bug): Could not resolve symbol [\S3PV], AE_NOT_FOUND (20200925/psargs-330) [ 4.307504] ACPI BIOS Error (bug): Could not resolve symbol [\S4CC], AE_NOT_FOUND (20200925/psargs-330) [ 4.307577] ACPI BIOS Error (bug): Could not resolve symbol [\S4HP], AE_NOT_FOUND (20200925/psargs-330) [ 4.307613] ACPI BIOS Error (bug): Could not resolve symbol [\S4PV], AE_NOT_FOUND (20200925/psargs-330) [ 4.307646] ACPI BIOS Error (bug): Could not resolve symbol [\S4AC], AE_NOT_FOUND (20200925/psargs-330) [ 4.326531] ACPI BIOS Error (bug): Could not resolve symbol [\S5CC], AE_NOT_FOUND (20200925/psargs-330) [ 4.326767] ACPI BIOS Error (bug): Could not resolve symbol [\S5HP], AE_NOT_FOUND (20200925/psargs-330) [ 4.329021] ACPI BIOS Error (bug): Could not resolve symbol [\S5PV], AE_NOT_FOUND (20200925/psargs-330) […] ``` This also happens with Linux 5.6 shipped with Dell’s pre-installed Ubuntu 20.04.1. No idea, why their QA does not fix these, probably in their firmware, before shipping.
Mario, it would be great, if you could escalate that internally.
Paul, just to double check - were you seeing these on the 1.1.1 FW? Or with the one the system launched with. Was this a regression upgrading to 1.1.1? Or you haven't done this yet?
Ah, sorry for not mentioning that. The system was shipped with 1.0.3, but I updated to 1.1.1 with fwupdmgr right away, so I do not know if it’s a regression in the 1.0.3 update. (And, sorry for not thinking of that, before making my statement. Though firmware updates should also be tested on the developer editions. ;-))
Thanks. I have one of these on hand myself and can see the interpreter has the same problem for me. It seems it's from SSDT2 table. The definition block mentions that these variables are listed as External but only used in that SSDT.
hi, may I know the current status of this issue?
Sorry, I’ll try to get the current logs from the user next week. Out of curiosity, does the Intel team have access to that system?
It’s still happening with BIOS 1.1.4 11/23/2020, and Linux 5.10.4. Mario, do you have ways to contact Dell’s firmware team?
Paul, checking the website 1.1.4 get released until 12/10. How could it have been checked on 11/23? Can you please double confirm if 1.1.4 has it fixed? I'll check with internal folks on it again. @Rui, This is definitely Dell BIOS issue. I think you can close it for kernel bugzilla. If 1.1.4 doesn't have it fixed, it's a timing thing related to last BIOS lifecycle and it should be in next BIOS.
(In reply to Mario Limonciello from comment #8) > Paul, checking the website 1.1.4 get released until 12/10. How could it > have been checked on 11/23? Can you please double confirm if 1.1.4 has it > fixed? I'll check with internal folks on it again. Sorry, for my ambiguity. The date *11/23/2020* comes from the DMI string, which is provided by the firmware. I guess, Dell still does some QA before actually releasing it to the public. I guess, it’s just a misunderstanding. The user actually updated the firmware today, and I looked at the Linux log messages today. > @Rui, > > This is definitely Dell BIOS issue. I think you can close it for kernel > bugzilla. If 1.1.4 doesn't have it fixed, it's a timing thing related to > last BIOS lifecycle and it should be in next BIOS. I change the status to resolved/documented.
Nice, Dell seems to have fixed the problem in version 1.2.5, released on January 11th, 2021 [1]. > Fixes: > - Fixed the issue where ACPI errors are reported when you run dmesg command > in Ubuntu operating system. If Dell now also starts adding bugzilla.kernel.org links into the Dell change-log, the whole process would almost be perfect. ;-) Mario, please pass on my thanks to the Dell firmware team. [1]: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=12n1m&oscode=ubt20&productcode=xps-13-9310-laptop