From: Stephen Boyd <swboyd@chromium.org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kalesh Singh <kaleshsingh@google.com>,
Tony Lindgren <tony@atomide.com>, Tri Vo <trong@android.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: Regression in Linux next with show wakeup sources stats in sysfs
Date: Wed, 14 Aug 2019 00:08:39 -0700 [thread overview]
Message-ID: <5d53b378.1c69fb81.31b2e.5077@mx.google.com> (raw)
In-Reply-To: <20190814063803.GY52127@atomide.com>
Quoting Tony Lindgren (2019-08-13 23:38:03)
> Hi all,
>
> Looks like commit 986845e747af ("PM / wakeup: Show wakeup sources stats
> in sysfs") has caused a regression in Linux next where I can now get
> some errors like this during the boot:
>
> kobject_add_internal failed for wakeup10 (error: -2 parent: usb)
>
> Any ideas why this might be happening? Maybe some deferred probe
> related issue?
>
Yeah! Take a look at this thread[1] and please test out patches I'm
throwing out there like a total cowboy(d).
[1] https://lkml.kernel.org/r/1565731976.8572.16.camel@lca.pw
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <swboyd@chromium.org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kalesh Singh <kaleshsingh@google.com>,
Tony Lindgren <tony@atomide.com>, Tri Vo <trong@android.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: Regression in Linux next with show wakeup sources stats in sysfs
Date: Wed, 14 Aug 2019 00:08:39 -0700 [thread overview]
Message-ID: <5d53b378.1c69fb81.31b2e.5077@mx.google.com> (raw)
In-Reply-To: <20190814063803.GY52127@atomide.com>
Quoting Tony Lindgren (2019-08-13 23:38:03)
> Hi all,
>
> Looks like commit 986845e747af ("PM / wakeup: Show wakeup sources stats
> in sysfs") has caused a regression in Linux next where I can now get
> some errors like this during the boot:
>
> kobject_add_internal failed for wakeup10 (error: -2 parent: usb)
>
> Any ideas why this might be happening? Maybe some deferred probe
> related issue?
>
Yeah! Take a look at this thread[1] and please test out patches I'm
throwing out there like a total cowboy(d).
[1] https://lkml.kernel.org/r/1565731976.8572.16.camel@lca.pw
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-14 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 6:38 Regression in Linux next with show wakeup sources stats in sysfs Tony Lindgren
2019-08-14 6:38 ` Tony Lindgren
2019-08-14 7:08 ` Stephen Boyd [this message]
2019-08-14 7:08 ` Stephen Boyd
2019-08-14 7:32 ` Tony Lindgren
2019-08-14 7:32 ` Tony Lindgren
2019-08-14 14:56 ` Stephen Boyd
2019-08-14 14:56 ` Stephen Boyd
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=5d53b378.1c69fb81.31b2e.5077@mx.google.com \
--to=swboyd@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=kaleshsingh@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tony@atomide.com \
--cc=trong@android.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.