You are not logged in.
Hi,
i got the following error message after Bios Upgrade:
[ 0.449031] ACPI BIOS Error (Bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.AC._PSR.AFN4], AE_NOT_FOUND (20220331/psargs-330)
[ 0.449046] ACPI Error: Abotrting method \_SB.PCI0.LPC0.EC0.AC._PSR due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
systemd log:
Aug 21 10:35:04 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.AC._PSR.>
Aug 21 10:35:04 kernel: fbcon: Taking over console
Aug 21 10:35:04 kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0.AC._PSR due to previous error>
Aug 21 10:35:04 kernel: ACPI: \_SB_.PCI0.LPC0.EC0_.AC__: Error reading AC Adapter state: AE_NOT_FOUND
machine: Lenovo Thinkpad P14s AMD Gen2
bios version: Lenovo ThinkPad T14/P14s Gen 2 AMD System Firmware R1MET49W, Version 1.19
Bios Update:
Prometheus (10.01.3273255 → 10.01.3478575)
System Firmware (0.1.17 → 0.1.19)
see https://fwupd.org/lvfs/devices/com.leno … T.firmware
$ uname -a
Linux 5.19.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 17 Aug 2022 13:48:51 +0000 x86_64 GNU/Linux
Whats the problem here? i seems that the error does not have any impacts, but i am not quite sure.
Please help. Any suggestions?
Last edited by arthurw (2022-08-22 07:05:52)
Offline
I had the same error on Intel Z390 until one of recent kernel updates. Seems no harm, just annoying messages.
https://bugzilla.kernel.org/show_bug.cgi?id=213023
Offline
@dimich, thanks for your QUICK answer. These messages are really annoying. Thanks for the link. And whats the cause of these error messages. I don't want to have them. Is there a reason to downgrade bios? Are there any problems witch battery?
Last edited by arthurw (2022-08-21 10:13:27)
Offline
And whats the cause of these error messages.
As i understand, some BIOS firmwares don't follow ACPI Specification strictly but the kernel is too strict.
I don't want to have them. Is there a reason to downgrade bios? Are there any problems witch battery?
I don't see reasons to downgrade BIOS if no other issues observed, but it's up to you. Maybe in future releases it will be fixed.
Offline
Maybe in future releases it will be fixed.
kernel or bios? kernel ok, but bios is very far in future i think.
so there is not anything other "we" can do than waiting?
Last edited by arthurw (2022-08-21 12:41:06)
Offline
kernel or bios? kernel ok, but bios is very far in future i think.
In my case those error messages appeared after regular kernel update and disappeared also after regular kernel update.
so there is not anything other "we" can do than waiting?
There are several variants.
Just ignore it.
File a bug to hardware vendor. I doubt they consider it as high priority since it's just an error messages in Linux.
Comment kernel ticket with your hardware description. Maybe someone would fix upstream for your hardware and don't break normal workflow for others.
Patch and compile custom kernel with those messages disabled. You'll need to maintain custom kernel yourself every time when upstream updated. There are also risk to miss useful messages in case of real errors.
Change hardware.
Offline
Thanks for your answer. i openened an kernel Ticket: https://bugzilla.kernel.org/show_bug.cgi?id=216390.
I will wait for some inputs until i resolve this issue. And just ignore the errors.
Last edited by arthurw (2022-08-21 13:39:05)
Offline
see: https://bugzilla.kernel.org/show_bug.cgi?id=216390
The DSDT refers to an external method AFN4():
External (_SB_.PCI0.LPC0.EC0_.AFN4, MethodObj) // 1 Arguments
It then makes use of this twice in the function that showed the unable to resolve:
If (((Local0 != ACDC) || (ACDC == 0xFF)))
{
CreateWordField (XX00, 0x00, SSZE)
CreateByteField (XX00, 0x02, ACST)
SSZE = 0x03
ACDC = Local0
If (ACDC)
{
AFN4 (0x01)
ACST = 0x00
}
Else
{
AFN4 (0x02)
ACST = 0x01
}ALIB (0x01, XX00)
}However nowhere in the DSDT or any of the SSDTs that you shared does AFN4 actually exist. This is a BIOS bug and the kernel can't do anything about it.
Last edited by arthurw (2022-08-22 07:04:49)
Offline