From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753763AbeDYWlt (ORCPT ); Wed, 25 Apr 2018 18:41:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:39458 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753466AbeDYWlo (ORCPT ); Wed, 25 Apr 2018 18:41:44 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 48FA521748 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Wed, 25 Apr 2018 18:41:40 -0400 From: Steven Rostedt To: "Rafael J. Wysocki" Cc: Linus Torvalds , Thomas Gleixner , Mark Salyzyn , Ingo Molnar , Peter Zijlstra , John Stultz , Peter Anvin , Michael Kerrisk , Prarit Bhargava , Pavel Machek , Kevin Easton , Dmitry Torokhov , Petr Mladek , Linux Kernel Mailing List , SergeySenozhatsky , Jonathan Corbet , linux-tip-commits@vger.kernel.org Subject: Re: [tip:timers/urgent] Revert: Unify CLOCK_MONOTONIC and CLOCK_BOOTTIME Message-ID: <20180425184140.6b6e524d@vmware.local.home> In-Reply-To: <5695751.Ycq0WTIcbj@aspire.rjw.lan> References: <5695751.Ycq0WTIcbj@aspire.rjw.lan> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 25 Apr 2018 22:57:12 +0200 "Rafael J. Wysocki" wrote: > FWIW, I run (64-bit) OpenSUSE 42.3 on the failing machine (Acer Aspire S5) with > my own kernel (custom config based on the distro one). > > The problem here is that the machine doesn't resume from S2R. It appears to > just hang somewhere around where we return to user space. However, to trigger > the issue it needs to stay in suspend for several minutes (not sure how many > exactly). If it is just back-to-back suspend/resume, it will resume correctly. I guess the question that needs to be asked is, have you tried a kernel with this commit reverted and it works? I'd play a bit going back and forth between two kernels, one with the commit and one without and no other differences, to make sure that is indeed the problem commit. -- Steve