Created attachment 300987 [details] Kernel messages (repeated parts are omitted) Today I found the kernel message is filled by the following repeating errors: [520711.531096] ACPI BIOS Error (bug): Attempt to CreateField of length zero (20211217/dsopcode-133) [520711.532405] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_OPERAND_VALUE) (20211217/psparse-529) [520711.535094] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_OPERAND_VALUE) (20211217/psparse-529) [520741.523722] ACPI BIOS Error (bug): Attempt to CreateField of length zero (20211217/dsopcode-133) [520741.525029] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_OPERAND_VALUE) (20211217/psparse-529) [520741.529127] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_OPERAND_VALUE) (20211217/psparse-529) It's happening every 30 seconds. The same error was observed before but hadn't been recurring like this. It turned out the error became recurring when I started to run Prometheus node-exporter on the machine. 30sec is exactly the interval I set to scrape metrics. I believe it happens when the node-exporter scrape some ACPI-related data. Hardware: HP 14-dk1xxx Laptop. It's actually used as an NAS so running 24/7. Kernel version: Linux mar 5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) x86_64 GNU/Linux I'm using `acpi_backlight=vendor` kernel option, but I can't remember why.
Created attachment 300988 [details] acpidump output
I confirm that reading /sys/class/hwmon/hwmon4/pwm1_enable triggers the error. $ ls -al /sys/class/hwmon/hwmon4/ total 0 drwxr-xr-x 3 root root 0 May 11 19:34 . drwxr-xr-x 3 root root 0 May 11 19:34 .. lrwxrwxrwx 1 root root 0 May 11 19:34 device -> ../../../hp-wmi -r--r--r-- 1 root root 4096 May 11 19:34 name drwxr-xr-x 2 root root 0 May 14 13:09 power -rw-r--r-- 1 root root 4096 May 14 13:09 pwm1_enable lrwxrwxrwx 1 root root 0 May 14 13:09 subsystem -> ../../../../../class/hwmon -rw-r--r-- 1 root root 4096 May 11 19:34 uevent
If you're using this as a NAS, I would anticipate you can W/A to avoid this BIOS bug by blacklisting hp-wmi.
(In reply to Mario Limonciello (AMD) from comment #3) > If you're using this as a NAS, I would anticipate you can W/A to avoid this > BIOS bug by blacklisting hp-wmi. Yeah you are right. This is what I'm doing now. It makes the error go away without noticeable side effect.
Thanks, I'll close this as documented then. A proper solution would need to come from the OEM.