Created attachment 299431 [details] Dmesg-5.14.15-with-ACPI-Divide-Error LXQt Desktop reports recently that the laptop battery is unavailable. OS: Arch Linux Kernel: 5.14.15 Laptop: MSI Bravo 17 Steps to reproduce: start laptop and login to desktop. Looking at the dmesg the following errors are found. [ 0.375136] ACPI Error: Divide by zero (20210604/utmath-478) [ 0.375145] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC.BAT1.UPBS due to previous error (AE_AML_DIVIDE_BY_ZERO) (20210604/psparse-529) [ 0.375151] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC.BAT1._BST due to previous error (AE_AML_DIVIDE_BY_ZERO) (20210604/psparse-529) [ 0.375157] ACPI: \_SB_.PCI0.SBRG.EC__.BAT1: _BST evaluation failed: AE_AML_DIVIDE_BY_ZERO [ 0.404716] ACPI Error: Divide by zero (20210604/utmath-478) [ 0.404725] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC.BAT1.UPBS due to previous error (AE_AML_DIVIDE_BY_ZERO) (20210604/psparse-529) [ 0.404732] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC.BAT1._BST due to previous error (AE_AML_DIVIDE_BY_ZERO) (20210604/psparse-529) [ 0.404737] ACPI: \_SB_.PCI0.SBRG.EC__.BAT1: _BST evaluation failed: AE_AML_DIVIDE_BY_ZERO [ 0.434701] ACPI Error: Divide by zero (20210604/utmath-478) [ 0.434710] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC.BAT1.UPBS due to previous error (AE_AML_DIVIDE_BY_ZERO) (20210604/psparse-529) [ 0.434716] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC.BAT1._BST due to previous error (AE_AML_DIVIDE_BY_ZERO) (20210604/psparse-529) [ 0.434721] ACPI: \_SB_.PCI0.SBRG.EC__.BAT1: _BST evaluation failed: AE_AML_DIVIDE_BY_ZERO I believe the recent upgraade from kernel 5.14.15 > 5.14.15 caused this error. I will downgrade to test and will confirm later. Dmesg is attached.
It turns out that a reboot magically made the error disappear. Closing the bug report.
It happened again today. New dmesg will be attached.
Created attachment 299489 [details] Dmesg-5.14.16-with-ACPI-Divide-Error
please attach the acpidump output of this machine.
Created attachment 301240 [details] MSI Bravo 17 ACPI dump
I have no idea why this is an regression because firmware uses a value from EC address space as the divisor, and this value is Zero. Can you double check if the problem can be reproduced in an earlier kernel release? If yes, can you please run git bisect to find out which commit introduces the problem? That would be really helpful for us to root cause the issue.
It happened a long time ago and only happened twice. I cannot reproduce it. Shall I close the bug report?
Thanks for the update. Bug closed.