https://bugzilla.kernel.org/show_bug.cgi?id=216230 --- Comment #17 from madcatx@xxxxxxxx --- My output from /sys/kernel/debug/dynamic_debug/control lists pinctrl_amd like this drivers/pinctrl/pinctrl-amd.c:1056 [pinctrl_amd]amd_gpio_probe =p "amd gpio driver loaded\012" drivers/pinctrl/pinctrl-amd.c:655 [pinctrl_amd]do_amd_gpio_irq_handler =p "Disabling spurious GPIO IRQ %d\012" drivers/pinctrl/pinctrl-amd.c:632 [pinctrl_amd]do_amd_gpio_irq_handler =p "Waking due to GPIO %d: 0x%x" IIRC this means that those debugging statements are enabled. The only relevant line from dmesg is this though: [ 0.668575] amd_gpio AMDI0030:00: amd gpio driver loaded I just noticed another case where the number of interrupts reached about 12000. With a bit of careful optimism I think that loading pinctrl_amd early during boot puts an early stop to the IRQ storm before the kernel intervenes and disables the interrupt channel. As for reproducibility, I think that the machine needs to run for some time before the problem can be "re-reproduced". This is why it looked like it was happening only on cold boots. Assuming there an EC connected to these GPIOs I guess it's some kind of timer overflow...? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
