Bug 220075 - ACPI BIOS errors on Honor Magicbook 2024 x14 (AE_ALREADY_EXISTS, AE_NOT_FOUND)
Summary: ACPI BIOS errors on Honor Magicbook 2024 x14 (AE_ALREADY_EXISTS, AE_NOT_FOUND)
Status: RESOLVED ANSWERED
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: acpi_bios
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-01 07:30 UTC by Karl Bach
Modified: 2025-05-01 10:54 UTC (History)
0 users

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


Attachments

Description Karl Bach 2025-05-01 07:30:14 UTC
I encountered multiple ACPI BIOS errors during boot. These appear to be related to incorrect or incomplete ACPI implementation in the firmware.

Here are messages from dmesg:
[    0.300082] ACPI BIOS Error (bug): Failure creating named object [\SCMD], AE_ALREADY_EXISTS (20240827/dsfield-637)
[    0.300114] ACPI Warning: NsLookup: Type mismatch on SCMD (Method), searching for (RegionField) (20240827/nsaccess-696)
[    0.305289] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.AZAL], AE_NOT_FOUND (20240827/dswload2-162)
[    0.305295] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
[    0.305299] ACPI: Skipping parse of AML opcode: Scope (0x0010)
[    0.306631] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.AZAL], AE_NOT_FOUND (20240827/dswload2-162)
[    0.306637] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
[    0.306640] ACPI: Skipping parse of AML opcode: Scope (0x0010)


The system does boot, but I am concerned about potential hardware or power management issues caused by incorrect ACPI definitions.
Moreover there are flickering display glitches (flickering) from time to time that I don't have in Windows but I don't know if the problems are related. 


System details:
- Laptop: Honor Magicbook X14 Plus 2024
- BIOS Version: 1.09
- Linux distro: Ubuntu 25.04
- Kernel version: 6.14.0-15


Let me know if more logs (full dmesg etc.) are needed — I can provide them.

Thanks!
Comment 1 Artem S. Tashkinov 2025-05-01 10:54:09 UTC
Those errors/warning messages are pretty normal as OEMs don't normally test their HW against Linux.

Unless something doesn't work at all, there's no need to worry.

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