Re: ACPI IRQ storm with 6.10

From: Rafael J. Wysocki
Date: Fri Aug 16 2024 - 14:29:40 EST


On Wed, Aug 14, 2024 at 8:48 AM Jiri Slaby <jirislaby@xxxxxxxxxx> wrote:
>
> On 14. 08. 24, 7:22, Jiri Slaby wrote:
> > Hi,
> >
> > one openSUSE's user reported that with 6.10, he sees one CPU under an
> > IRQ storm from ACPI (sci_interrupt):
> > 9: 20220768 ... IR-IO-APIC 9-fasteoi acpi
> >
> > At:
> > https://bugzilla.suse.com/show_bug.cgi?id=1229085
> >
> > 6.9 was OK.
> >
> > With acpi.debug_level=0x08000000 acpi.debug_layer=0xffffffff, there is a
> > repeated load of:
> >> evgpe-0673 ev_detect_gpe : Read registers for GPE 6D:
> >> Status=20, Enable=00, RunEnable=4A, WakeEnable=00
>
> 0x6d seems to count excessively (10 snapshots every 1 second):
> > /sys/firmware/acpi/interrupts/gpe6D: 82066 EN STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 86536 EN STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 90990 STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 95468 EN STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 100282 EN STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 105187 STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 110014 STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 114852 STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 119682 STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 124194 STS enabled unmasked
> > /sys/firmware/acpi/interrupts/gpe6D: 128641 EN STS enabled unmasked
>
> acpidump:
> https://bugzilla.suse.com/attachment.cgi?id=876677
>
> DSDT:
> https://bugzilla.suse.com/attachment.cgi?id=876678
>
> > Any ideas?

GPE 6D is listed in _PRW for some devices, so maybe one of them
continues to trigger wakeup events?

You can ask the reporter to mask that GPE via "echo mask >
/sys/firmware/acpi/interrupts/gpe6D" and see if the storm goes away
then.

The only ACPI core issue introduced between 6.9 and 6.10 I'm aware of
is the one addressed by this series

https://lore.kernel.org/linux-acpi/22385894.EfDdHjke4D@xxxxxxxxxxxxx/

but this is about the EC and the problem here doesn't appear to be
EC-related. It may be worth trying anyway, though.