On 27 June 2017 at 16:47, Andy Shevchenko <andy.shevchenko@xxxxxxxxx> wrote: > Tom, thanks for this. > I would speculate that the problem might be in the certain device > drivers. It would be nice to get statistics which wakeup source > generates more hits. Is this something I can determine without CONFIG_ACPI_DEBUG being enabled? I don't get anything in dmesg other than indications that it's resuming and then sleeping again every second or so. [ 45.463907] PM: Suspending system (freeze) [ 47.703216] PM: suspend of devices complete after 2028.170 msecs [ 47.721329] PM: late suspend of devices complete after 18.108 msecs [ 47.723153] ACPI : EC: interrupt blocked [ 47.757801] PM: noirq suspend of devices complete after 35.746 msecs [ 47.757802] PM: suspend-to-idle [ 48.944708] Suspended for 0.779 seconds [ 48.945030] ACPI : EC: interrupt unblocked [ 48.980728] PM: noirq resume of devices complete after 35.924 msecs [ 48.982265] ACPI : EC: interrupt blocked [ 49.027946] PM: noirq suspend of devices complete after 47.016 msecs -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
