[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+b4Kqdq2z6Z23P+SGQ1GYg+VMBmKG=MXL-EPZ6PfugtgB6ENQ@mail.gmail.com>
Date: Tue, 27 Jun 2017 20:54:08 +1000
From: Tom Lanyon <tom@...shoeco.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux ACPI <linux-acpi@...r.kernel.org>,
Linux PM <linux-pm@...r.kernel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Darren Hart <dvhart@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Mario Limonciello <mario.limonciello@...l.com>,
Jérôme de Bretagne
<jerome.debretagne@...il.com>, "Zheng, Lv" <lv.zheng@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] ACPI / sleep: EC-based wakeup from suspend-to-idle on
recent systems
On 27 June 2017 at 16:47, Andy Shevchenko <andy.shevchenko@...il.com> 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
Powered by blists - more mailing lists