Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752278AbdGaOFA (ORCPT <rfc822;w@1wt.eu>);
        Mon, 31 Jul 2017 10:05:00 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:38753 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751862AbdGaOE7 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 31 Jul 2017 10:04:59 -0400
Date: Mon, 31 Jul 2017 16:04:40 +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: <d0d95780-979f-240a-7c1e-3ce53d438e02@intel.com>
Message-ID: <alpine.DEB.2.20.1707311603420.2314@nanos>
References: <4d6b511a-61d5-3c5e-a406-9f71d83670b6@linux.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> <alpine.DEB.2.20.1707281734240.1828@nanos> <e0b96b01-a033-4e28-08c8-fc04f8edd2fc@intel.com> <alpine.DEB.2.20.1707310935370.2314@nanos>
 <412a3ab0-4ae5-b27a-0b2d-d2e03b27a999@intel.com> <alpine.DEB.2.20.1707311026170.2314@nanos> <d0d95780-979f-240a-7c1e-3ce53d438e02@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
Content-Length: 1637
Lines: 48

On Mon, 31 Jul 2017, Tomi Sarvela wrote:
> On 31/07/17 11:29, Thomas Gleixner wrote:
> > On Mon, 31 Jul 2017, Tomi Sarvela wrote:
> > > On 31/07/17 10:45, Thomas Gleixner wrote:
> > > > On Mon, 31 Jul 2017, Tomi Sarvela wrote:
> > > > > On 28/07/17 19:26, Thomas Gleixner wrote:
> > > > > > Did you change anything else compared to the tests before ?
> > > > > 
> > > > > I did check that the problem persisted in linus-HEAD before testing
> > > > > your
> > > > > patch. The testing was done in order (reading from console logs I
> > > > > happen
> > > > > to
> > > > > still have in one window):
> > > > 
> > > > What I still do not understand is why this would affect the suspend path
> > > > in
> > > > any way.
> > > > 
> > > > Can you remove the previous patch and apply the one below. If it
> > > > resumes,
> > > > please provide the data from the trace buffer again.
> > > 
> > > No such luck. ELK hangs in the suspend-test with earlier patch removed,
> > > this
> > > added. Checked again that the power-led is on, no serial output.
> > > 
> > > Tree not pulled: still testing against the previous head -rc2, not current
> > > 4.13.0-rc3
> > 
> > Shouldn't make a difference. Can you please try the following:
> > 
> > Offline CPU1 before invoking suspend.
> > 
> > # echo 0 >/sys/devices/system/cpus/cpu1/offline
> 
> Tested with your latest patch (irq_trace_state):
> 
> echo 0 >/sys/devices/system/cpu/cpu1/online
> 
> ./scripts/run-tests.sh -vt igt@gem_exec_suspend@basic-s3 -x devices

So this "igt@gem_exec_suspend@basic-s3" thingy is that executing anything
extra aside of 'echo mem > /sys/power/state'?

Thanks,

	tglx