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 S1757715AbbLBVbm (ORCPT <rfc822;w@1wt.eu>);
	Wed, 2 Dec 2015 16:31:42 -0500
Received: from mail-yk0-f176.google.com ([209.85.160.176]:35046 "EHLO
	mail-yk0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751196AbbLBVbj (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 2 Dec 2015 16:31:39 -0500
MIME-Version: 1.0
In-Reply-To: <20151202205745.GA28256@kroah.com>
References: <CALAqxLUmdjwS0sa7uKUF_bzzLqi_npO7Vh2MTLST4B+BCObKjA@mail.gmail.com>
	<CALAqxLVqsSqAmAuKXQkFacCv6ofEKoinvu3_viPJeqvZ5ZoNOg@mail.gmail.com>
	<20151202205745.GA28256@kroah.com>
Date: Wed, 2 Dec 2015 13:31:38 -0800
Message-ID: <CALAqxLWjBP=iyAb=Rm3Z5Y3RNPwFy-KGmag0a5KGu97VYRO+aQ@mail.gmail.com>
Subject: Re: [REGRESSION] b8b2c7d845 breaks suspend/resume in qemu
From: John Stultz <john.stultz@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: martin.wilck@ts.fujitsu.com,
        =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= 
	<u.kleine-koenig@pengutronix.de>,
        lkml <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Dec 2, 2015 at 12:57 PM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Wed, Dec 02, 2015 at 12:46:10PM -0800, John Stultz wrote:
>> On Wed, Dec 2, 2015 at 12:39 PM, John Stultz <john.stultz@linaro.org> wrote:
>> > Hey Uwe,
>> >
>> > So I recently noticed that my alarmtimer suspend/resume tests
>> > (selftests/timers/alartimer-suspend.c) were getting stuck testing w/
>> > 4.4-rc kernels when running under qemu (x86_64).
>> >
>> > I've bisected this back to: b8b2c7d845 (base/platform: assert that
>> > dev_pm_domain callbacks are called unconditionally).
>> >
>> > I've not yet spent done any further analysis (bisecting it down, after
>> > some user-error, ate up my morning). But I wanted to see if there were
>> > any initial suggestions for solving this.
>>
>> Just one other quick note: Reverting this commit against 4.4-rc3 seems
>> to work as well.
>
> There's a proposed patch to resolve this on the mailing list, "Subject:
> [PATCH] base/platform: fix panic when probe function is NULL" from
> Martin, but I think he's going to send me an updated version before I
> forward it on to Linus.
>
> It should resolve your issue, can you verify that?

Yep. That fix seems to avoid the problem for me.

thanks
-john