From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: John Stultz <john.stultz@linaro.org>, martin.wilck@ts.fujitsu.com
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] b8b2c7d845 breaks suspend/resume in qemu
Date: Wed, 2 Dec 2015 12:57:45 -0800 [thread overview]
Message-ID: <20151202205745.GA28256@kroah.com> (raw)
In-Reply-To: <CALAqxLVqsSqAmAuKXQkFacCv6ofEKoinvu3_viPJeqvZ5ZoNOg@mail.gmail.com>
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?
thanks,
greg k-h
next prev parent reply other threads:[~2015-12-02 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 20:39 [REGRESSION] b8b2c7d845 breaks suspend/resume in qemu John Stultz
2015-12-02 20:46 ` John Stultz
2015-12-02 20:57 ` Greg Kroah-Hartman [this message]
2015-12-02 21:31 ` John Stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151202205745.GA28256@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.wilck@ts.fujitsu.com \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox