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 S1751654AbdG0UNg (ORCPT <rfc822;w@1wt.eu>);
        Thu, 27 Jul 2017 16:13:36 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:55941 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751587AbdG0UNf (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 27 Jul 2017 16:13:35 -0400
Date: Thu, 27 Jul 2017 22:13:18 +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,
        linux-kernel@vger.kernel.org
Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo
In-Reply-To: <alpine.DEB.2.20.1707272138080.2368@nanos>
Message-ID: <alpine.DEB.2.20.1707272209130.2368@nanos>
References: <4d6b511a-61d5-3c5e-a406-9f71d83670b6@linux.intel.com> <alpine.DEB.2.20.1707241711020.1988@nanos> <864ff133-815c-0c7f-5e36-fdcc32d0261d@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>
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

On Thu, 27 Jul 2017, Thomas Gleixner wrote:
> On Thu, 27 Jul 2017, Tomi Sarvela wrote:
> 
> > On 27/07/17 10:42, Thomas Gleixner wrote:
> > > On Thu, 27 Jul 2017, Tomi Sarvela wrote:
> > > > On 26/07/17 17:26, Thomas Gleixner wrote:
> > > > > So reverting that commit does not help. Does it help on your machine?
> > > > 
> > > > Yes. Reverting it does not cause the machine to lock up on resume.
> > > > 
> > > > I haven't tested if the machine locks up later on, but at least it
> > > > survives
> > > > couple of s/r cycles.
> > > 
> > > Can you please try to add 'nohpet' to the kernel command line?
> > 
> > Option nohpet didn't change anything, still hangs on s/r.
> 
> Ok. Was a shot in the dark. I tried on a similar machine, but that one
> resumes fine (except that the AHCI controller plays silly buggers, but
> nothing interrupt related). I might have access to another core2duo machine
> tomorrow.
> 
> I'll send you a debug patch shortly, but can you please first check when
> the wreckage happens by testing the states in
> 
>     /sys/power/pm_test
> 
> freezer
> devices
> platform
> processors
> core

Actually for suspend to ram we only have

	 freezer, devices, platform

I assume it's platform because that is where the actual interrupt
suspend/resume happens.

If that survives, then it's the low level architecture s/r code which
fiddles with the interrupt controllers and leaves them in a state which is
not known to the core code.

Thanks,

	tglx