Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#76612 - ACPI BIOS Error (bug): Could not resolve symbol

Attached to Project: Arch Linux
Opened by Klimenko Maxim Sergievich (scry3r) - Thursday, 17 November 2022, 20:30 GMT
Last edited by Toolybird (Toolybird) - Thursday, 17 November 2022, 21:26 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: ACPI BIOS Error (bug): Could not resolve symbol
[ +0,000332] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-330)
[ +0,000009] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ +0,000343] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-330)
[ +0,000006] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ +0,000136] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-330)
[ +0,000007] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ +0,000125] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-330)
[ +0,000007] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
   dmesglog-222111172022.log (87.4 KiB)
   222811172022 (937.1 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 17 November 2022, 21:26 GMT
Reason for closing:  Upstream
Additional comments about closing:  https://bugzilla.kernel.org/show_bug.cgi ?id=202585
Comment by Toolybird (Toolybird) - Thursday, 17 November 2022, 21:08 GMT
Is there an actual problem here or you just like reporting log spam?

These kinds of errors are reported all over the internet. It's usually due to a buggy BIOS/firmware or a pedantic kernel. If it's a kernel issue then it needs to be reported to the kernel folks. But see for example [1][2] which are marked "WILL_NOT_FIX". Have you updated machine's BIOS/firmware to the latest from manufacturer?

[1] https://bugzilla.kernel.org/show_bug.cgi?id=202585
[2] https://bugzilla.kernel.org/show_bug.cgi?id=202867

Comment by Klimenko Maxim Sergievich (scry3r) - Thursday, 17 November 2022, 21:22 GMT
Sorry, I forgot about search

And yes I have latest bios. As I can see is best to close this bug.

Loading...