On Fri, Feb 24, 2023, at 6:52 AM, Dave Voutila wrote: > "Brian Conway" <bcon...@rcesoftware.com> writes: > >> Greetings. I am soliciting feedback on a patch to detect and mitigate >> uncontrolled ACPI GPE interrupt storms. >> >> Rationale: There have been a number of threads in the recent past on bugs@ >> and misc@ with acpi0 spinning a CPU at 100% [1][2][3][4]. The immediate >> cause is likely a buggy BIOS and its ACPI implementation. However, this type >> of bug is not exclusive to no-name hardware from China, nor is it specific >> to a particular hardware vendor, BIOS vendor, or GPE pin. Hardware that is >> or was affected can include Intel [5], Lenovo [6], HP [7], ASUS [8], and >> Apple [9]. >> >> I have been testing with a half-dozen ACPI-equipped systems in various >> states: storming and behaving, booting and resuming, 7.2 and -current, SMALL >> and not. The attached diff uses a minimum 5-second evaluation window, driven >> by the firing of ACPI GPE interrupts (no additional accounting thread, etc). >> An uncontrolled GPE storm will be logged as such (real number): >> > > How about zzz and ZZZ cycles? I think you might be using the wrong clock > so I hypothesize this breaks. See getuptime(9).
My apologies on the impreciseness of "resuming". Yes, I have tested zzz and ZZZ successfully, but certainly additional testing would be appreciated. I chose getuptime(9) for the tracking window as a monotonic source with a simple return type. Brian
