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 S1752389AbdGaPpa (ORCPT <rfc822;w@1wt.eu>);
        Mon, 31 Jul 2017 11:45:30 -0400
Received: from mga11.intel.com ([192.55.52.93]:33262 "EHLO mga11.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752106AbdGaPp3 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 31 Jul 2017 11:45:29 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.40,442,1496127600"; 
   d="scan'208";a="999181535"
Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Martin Peres <martin.peres@linux.intel.com>, jeffy.chen@rock-chips.com,
        linux-kernel@vger.kernel.org
References: <4d6b511a-61d5-3c5e-a406-9f71d83670b6@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>
 <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.1707311701480.2314@nanos>
From: Tomi Sarvela <tomi.p.sarvela@intel.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Message-ID: <b9280675-fe26-da23-2c6b-fce7dcc3e762@intel.com>
Date: Mon, 31 Jul 2017 18:44:20 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1707311701480.2314@nanos>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 31/07/17 18:06, 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.
> 
> Can you please remove the patch. And try the following:
> 
> # echo N > /sys/module/printk/parameters/console_suspend
> 
> # echo mem > /sys/power/state
> 
> and log the output of the serial console. That way we might get a clue
> where it gets stuck.

I'm afraid it hangs right away. No response from SSH, no output to serial.

Tomi
-- 
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo