ACPI BIOS Error (bug) after wakening the PC from sleep

[antoniovalos]

I runned dmesg command on my PC, and I got an free-of-errors output, then I put my PC on sleep state, and waked it on again, and runned dmesg again, and I got this following error:

Code: Select all

[  110.940636] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.CHN0.DRV0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
[  110.940642] ACPI Error: Aborting method \_SB.PCI0.SAT1.CHN0.DRV0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

The system is working well, but this error worries me, am I doing any configuration wrong to get this error?

[rab0171610]

I would not be bothered by it if the system is working well and resumes from sleep normally. Sometimes these types of acpi errors appear with new kernel versions and disappear in later ones. They are often benign.
ACPI specifications are catered towards Microsoft Windows by motherboard manufacturers. They do not always play nice with the Linux Kernel.
If the error really bothers you, I can only suggest trying one of two things:
Try to update the BIOS or boot with the kernel parameter "libata.noacpi=1" , which may disable acpi for the motherboard sata.
Neither are guaranteed to be a solution.

[Iguana8649]

Additionally, if you want to go down the rabbit hole and "waste"/spend 80+ hours learning "stuff", you can try to disassemble the part of your BIOS responsible for mapping those identifiers to devices.

"Debug ACPI DSDT and SSDT with ACPICA Utilities" is a good place to start as any.

As usual, no warranties, expressed or otherwise, come with such post, meaning if you crash your PC, start a thermonuclear war or poke an alien species with xenophobic instincts in the eye, you're on your own.

[antoniovalos]

Before I put my PC on sleep mode, the dmesg output shows the message as warnings:

Code: Select all

[    3.473482] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20220331/utaddress-204)
[    3.473490] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[    3.473493] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20220331/utaddress-204)
[    3.473497] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
[    3.473499] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[    3.473500] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20220331/utaddress-204)
[    3.473503] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
[    3.473506] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[    3.473507] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20220331/utaddress-204)
[    3.473509] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)

[rab0171610]

This is a message indicating that the firmware and OS are trying to access the same sensor or data register of a hardware device. For a full technical explanation see comment #37:
https://bugzilla.kernel.org/show_bug.cgi?id=204807#c37
It has appeared for years on various systems. Per the above link and an old thread:
viewtopic-p-8690372.html?sid=2c553bfbe6 ... 8c9a503097
You could try booting with:

Code: Select all

acpi_enforce_resources=no

or

Code: Select all

acpi_enforce_resources=lax

Code: Select all

acpi_enforce_resources= [ACPI]
            { strict | lax | no }
            Check for resource conflicts between native drivers
            and ACPI OperationRegions (SystemIO and SystemMemory
            only). IO ports and memory declared in ACPI might be
            used by the ACPI subsystem in arbitrary AML code and
            can interfere with legacy drivers.

            strict (default): access to resources claimed by ACPI
            is denied; legacy drivers trying to access reserved
            resources will fail to bind to device using them.

            lax: access to resources claimed by ACPI is allowed;
            legacy drivers trying to access reserved resources
            will bind successfully but a warning message is logged.

            no: ACPI OperationRegions are not marked as reserved,
            no further checks are performed.