https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #31 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- OK so that does confirm that you're getting an interrupt firing while asleep and it's waking the system continuously. I have a strong suspicion it's caused by the stable backport of this specific commit: https://github.com/torvalds/linux/commit/635a750d958e158e17af0f524bedc484b27fbb93 This commit fixes an interrupt storm reported on another system, so it's surprising that it causes a problem on yours. But I think this may have caused the GPIO for the touchpad (which is used for "attention") to be programmed as and s0i3 wake source and cause that wake storm. 1. Can you please add your acpidump for your system? I need to look at _CRS for the touchpad and confirm that's intended behavior from the firmware or not. I'll cross reference some of my reference hardware as well as I've not encountered this myself. 2. To confirm my suspicion could you make a local change to turn off the code caused by that and instead document what's happening? basically this local patch: diff --git a/drivers/pinctrl/pinctrl-amd.c b/drivers/pinctrl/pinctrl-amd.c index 20bd97a603d9c..55907c82822d5 100644 --- a/drivers/pinctrl/pinctrl-amd.c +++ b/drivers/pinctrl/pinctrl-amd.c @@ -775,6 +775,9 @@ static int amd_pinconf_set(struct pinctrl_dev *pctldev, unsigned int pin, arg = pinconf_to_config_argument(configs[i]); pin_reg = readl(gpio_dev->base + pin*4); + dev_info(&gpio_dev->pdev->dev, "set config pin %d to %04x\n", pin, param); + continue; + switch (param) { case PIN_CONFIG_INPUT_DEBOUNCE: ret = amd_gpio_set_debounce(gpio_dev, pin, arg); Please also report if this avoids the issue on your side. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
