On Mon, Aug 25, 2025 at 06:34:48PM +0300, Andy Shevchenko wrote: > On Mon, Jun 30, 2025 at 02:40:28PM -0400, Mario Limonciello wrote: > > On 6/30/2025 3:14 AM, Askar Safin wrote: > > > ---- On Fri, 27 Jun 2025 07:58:15 +0400 Mario Limonciello <superm1@xxxxxxxxxx> wrote --- > > > > That's odd. It should be made when the PMC core driver binds. Maybe > > > > others will know what's missing here. > > > > > > Command "grep -r -E -I last_hw_sleep ." in culpit kernel (1796f808e4bb2c074824d) > > > shows nothing. (This is somewhere around 6.1). > > > > > > So, culpit commit is too old. > > > > > > If you want, I can retest this thing on current master and on current master with > > > revert 1796f808e4bb2c074824d. > > > > > > > I see in your bad config interrupt 14 is waking the system. In the good > > > > config interrupt 8 is waking it. > > > > > > > > What is in /proc/interrupts? > > > > > > /proc/interrupts from culpit kernel: https://paste.debian.net/1382819/ > > > > > > -- > > > Askar Safin > > > https://types.pl/@safinaskar > > > > > > > Looks like your interrupt 14 is ACPI device INTC1085:00. > > > > Some quick searches this seems to be an Intel GPIO controller. > > > > Andy, > > > > Any ideas how to debug next? > > I believe it's related to the touchpad (can you check that wake happens due to > actually IRQ on pin 355 of the GPIO controller? In other words we need to enable debug of the pin control subsystem and see what it will print in dmesg. -- With Best Regards, Andy Shevchenko
