From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751990AbdGaIfH (ORCPT <rfc822;w@1wt.eu>);
        Mon, 31 Jul 2017 04:35:07 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:36913 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751264AbdGaIfG (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 31 Jul 2017 04:35:06 -0400
Date: Mon, 31 Jul 2017 10:35:00 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>
cc: Martin Peres <martin.peres@linux.intel.com>, jeffy.chen@rock-chips.com,
        LKML <linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo
In-Reply-To: <1d2c51f3-a655-2223-68a9-e6d700e7d8e1@intel.com>
Message-ID: <alpine.DEB.2.20.1707311032380.2314@nanos>
References: <4d6b511a-61d5-3c5e-a406-9f71d83670b6@linux.intel.com> <alpine.DEB.2.20.1707241833270.1988@nanos> <2ecc8ffd-e041-2d53-6f33-e91b3ec701eb@linux.intel.com> <a585961a-3e07-b086-577a-729ad20d9935@intel.com> <67de95b4-a869-d897-e76c-17c974fb21a6@linux.intel.com>
 <alpine.DEB.2.20.1707261625010.2186@nanos> <862ba91e-9185-89a8-da81-63bb42ea565d@intel.com> <alpine.DEB.2.20.1707270939290.3109@nanos> <ddc71535-02de-5b42-934f-70bc5ad43bb7@intel.com> <alpine.DEB.2.20.1707272138080.2368@nanos> <alpine.DEB.2.20.1707272209130.2368@nanos>
 <alpine.DEB.2.20.1707272306310.2368@nanos> <7287f845-1012-51af-e696-99d26bcb9b7f@intel.com> <alpine.DEB.2.20.1707281439120.1986@nanos> <alpine.DEB.2.20.1707281514000.1986@nanos> <f7f52efa-f45c-7e9e-e407-a72c13a55089@intel.com> <alpine.DEB.2.20.1707281609250.1986@nanos>
 <d7c5c87e-7ff4-6599-4f93-5ea4a9ae17b4@intel.com> <alpine.DEB.2.20.1707281649210.1828@nanos> <1d2c51f3-a655-2223-68a9-e6d700e7d8e1@intel.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Rafael,

On Fri, 28 Jul 2017, Tomi Sarvela wrote:
>          rtcwake-1332  [000] d..1    64.411112: suspend_device_irqs:
> presuspend 8 state 00401200
>          rtcwake-1332  [000] d..1    64.411112: __irq_disable: predisable 8
> state 00401200
>          rtcwake-1332  [000] d..1    64.411113: __irq_disable: postdisable 8
> state 00411200
>          rtcwake-1332  [000] d..1    64.411114: suspend_device_irqs:
> postsuspend 8 state 00411200
>          rtcwake-1332  [000] d..1    64.411115: suspend_device_irqs:
> presuspend 9 state 00403300
>          rtcwake-1332  [000] d..1    64.411115: __irq_disable: predisable 9
> state 00403300
>          rtcwake-1332  [000] d..1    64.411116: __irq_disable: postdisable 9
> state 00413300
>          rtcwake-1332  [000] d..1    64.411116: suspend_device_irqs:
> postsuspend 9 state 00413300
>          rtcwake-1332  [000] d..1    64.411117: suspend_device_irqs:

I'm trying to analyze that suspend/resume problem. While staring at the
trace Tomi provided I noticed, that neither the RTC irq nor the ACPI irq
have the wakeup armed bit set, but the system resumes from an RTC
interrupt. That's inconsistent at least, or am I missing something
essential?

Thanks,

	tglx