ACPI BIOS Error (bug): Could not resolve symbol yadda yadda

[Goatmilk]

After I've learned the command "sudo dmesg -l err" while fiddling around with my Virtualbox machine and proudly mastered the art to copy it into a terminal, I thought I might run it on my actual MX system just to see what comes up.

Oops...

owl@Max:~
$ sudo dmesg -l err   
[sudo] password for owl:     
[    0.094601] x86/cpu: SGX disabled by BIOS.
[    1.004147] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-332)
[    1.004161] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[    1.004298] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-332)
[    1.004308] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[    1.004369] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-332)
[    1.004378] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[    1.004432] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20220331/psargs-332)
[    1.004441] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[11121.285901] iwlwifi 0000:01:00.0: No beacon heard and the time event is over already...
[11127.643854] iwlwifi 0000:01:00.0: No beacon heard and the time event is over already...
owl@Max:~

From what I could glean from the webs there doesn't seem to be much I could do about the ACPI whatnots, and the beacon thing seems to point to a low or unsteady wifi.

Quite frankly, I didn't notice anything untoward while running my laptop, but given my not so vast amount of experience, that probably doesn't say much. Anyway, I never noticed any connection problems, either. YouTube videos load slowly, but I should probably recheck my over-zealous Firefox-hardening-settings for those. Following some security guru site, I've adjusted so much in the poor Foxy's settings that I'm quite surprised it still runs at all...

So, what do you think about those errors above? What would you do about them?

 

[ron.alan]

Most acpi errors are meaningless. Does your computer run okay after boot up? If so, nothing to worry about. I get acpi errors on every boot up ever since I've been running Linux for over 12 years now.

 

[Trml]

I agree with @ron.alan, you can likely disregard those errors.

I've adjusted so much in the poor Foxy's settings that I'm quite surprised it still runs at all

Firefox still has a comprehensive user-profile feature. It can come in clutch to test new settings, also permanently keep a test profile. To use it:

$ firefox -P &

 

[Condobloke]

@Goatmilk The sight of this should make you feel better....

brian@brian-desktop:~$ sudo dmesg -l err
[sudo] password for brian:
[ 0.140216] DMAR: [Firmware Bug]: No firmware reserved region can cover this
RMRR [0x0000000078800000-0x0000000088ffffff], contact BIOS vendor for fixes

[ 0.151160] x86/cpu: SGX disabled by BIOS.

[ 5.981372] usb 1-1: 1:1: cannot get freq at ep 0x1

[ 12.243399] usb 1-1: 1:1: cannot get freq at ep 0x1

[ 12.255388] usb 1-1: 1:1: cannot get freq at ep 0x1
brian@brian-desktop:~$

 

[Condobloke]

This is Linux Mint 22.2 which runs quite perfectly

 

[ron.alan]

If you want to stop seeing these ACPI errors flash by on startup, do this:

1) Open the grub file at /etc/default/grub. I use the text editor Pluma, so in terminal:
sudo pluma /etc/default/grub
If you use a different editor, change "pluma" to whatever you use.

2) Find the line: GRUB_CMDLINE_LINUX_DEFAULT="quiet" .
Change it to read: GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 splash"
Save and exit.

3) Then run: sudo update-grub

Source: https://easylinuxtipsproject.blogspot.com/p/faq-3.html#ID19
(This website focuses on Mint and Ubuntu, but a lot of the advice given on it works on most Linux distros.)

NOTE: It might be a good idea to make a backup copy of the grub file before making changes.

 

[osprey]

From what I could glean from the webs there doesn't seem to be much I could do about the ACPI whatnots, and the beacon thing seems to point to a low or unsteady wifi.

Quite frankly, I didn't notice anything untoward while running my laptop, but given my not so vast amount of experience, that probably doesn't say much. Anyway, I never noticed any connection problems, either. YouTube videos load slowly, but I should probably recheck my over-zealous Firefox-hardening-settings for those. Following some security guru site, I've adjusted so much in the poor Foxy's settings that I'm quite surprised it still runs at all...

So, what do you think about those errors above? What would you do about them?

These posts may be of interest on the ACPI error messages: https://linux.org/threads/linux-not...ows-11-i-cant-use-arch-btw.51041/#post-238885, and, https://linux.org/threads/ubuntu-23-04.44740/#post-189829.

If, as you found, the machine works well, then the ACPI messages can be ignored, as mentioned by others. However, they are not meaningless since they represent issues that manufacturers have not attended to by not adhering to the full implementation of the protocols set for ACPI functioning. The linux kernel on the other hand, understands the protocol and compliance, and basically points out where that has not been fulfilled. As mentioned in one of the above threads, one needs to appeal to the hardware manufacturers to deal with the issue rather than linux developers.

 

[Condobloke]

from memory, info gleaned when I had similar dramas (+ a few other bits and pieces thrown in ).... the acpi errors are largely a lack of interest on the part of motherboard manufacturers

They have the ability to clean up the mess, but simply do not bother