https://bugzilla.kernel.org/show_bug.cgi?id=221556

            Bug ID: 221556
           Summary: Suppress identical repeating ACPI errors
           Product: ACPI
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: Other
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Some firmware-originated ACPI/AML errors can repeat indefinitely and flood logs
despite being non-actionable from the OS side.

Example from an HP Omnibook 7 (latest firmware F.12):
```
[ 1763.129408] ACPI Error: No handler for Region [CMS0] (000000005d636f1e)
[SystemCMOS] (20251212/evregion-131)
[ 1763.129427] ACPI Error: Region SystemCMOS (ID=5) has no handler
(20251212/exfldio-261)
[ 1763.129441] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0._Q33 due to
previous error (AE_NOT_EXIST) (20251212/psparse-529)

[ 3546.963906] ACPI Error: No handler for Region [CMS0] (000000005d636f1e)
[SystemCMOS] (20251212/evregion-131)
[ 3546.963939] ACPI Error: Region SystemCMOS (ID=5) has no handler
(20251212/exfldio-261)
[ 3546.963962] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0._Q33 due to
previous error (AE_NOT_EXIST) (20251212/psparse-529)

[ 5330.825259] ACPI Error: No handler for Region [CMS0] (000000005d636f1e)
[SystemCMOS] (20251212/evregion-131)
[ 5330.825280] ACPI Error: Region SystemCMOS (ID=5) has no handler
(20251212/exfldio-261)
[ 5330.825295] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0._Q33 due to
previous error (AE_NOT_EXIST) (20251212/psparse-529)
```

These messages recur periodically for the lifetime of the system and
continuously pollute dmesg/journal logs.

This appears to be firmware behavior associated with an EC query method (_Q33)
repeatedly attempting to access a SystemCMOS operation region without a
registered handler.

I am not requesting that the kernel hide or ignore the initial error.

However, would it make sense to:

 * ratelimit identical ACPICA runtime errors, or
 * suppress repeated identical AML failures after the first few occurrences per
boot/session?

Many other kernel subsystems already ratelimit persistent
firmware/hardware-originated log spam.

They don't occur too often but sometimes they are logged quite regularly and
they fill up my dmesg log without any recourse.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to