From: Stephen Boyd <swboyd@chromium.org>
To: Qian Cai <cai@lca.pw>, Tri Vo <trong@android.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
rafael@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: "PM / wakeup: Show wakeup sources stats in sysfs" causes boot warnings
Date: Tue, 13 Aug 2019 17:35:10 -0700 [thread overview]
Message-ID: <5d53573f.1c69fb81.a2ac0.65f6@mx.google.com> (raw)
In-Reply-To: <1565731976.8572.16.camel@lca.pw>
Quoting Qian Cai (2019-08-13 14:32:56)
> The linux-next commit "PM / wakeup: Show wakeup sources stats in sysfs" [1]
> introduced some baddies during boot on several x86 servers. Reverted the commit
> fixed the issue.
>
> [1] https://lore.kernel.org/lkml/20190807014846.143949-4-trong@android.com/
>
> [ 39.195053][ T1] serio: i8042 KBD port at 0x60,0x64 irq 1
> [ 39.197347][ T1] kobject_add_internal failed for wakeup (error: -2 parent:
Also, this is weird. Why is the kobject name just 'wakeup' and not
something like wakeup0 or wakeup1? This is why we're seeing the lockdep
warning happen after, but I'm not sure why the name doesn't have a
number associated with it.
next prev parent reply other threads:[~2019-08-14 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 21:32 "PM / wakeup: Show wakeup sources stats in sysfs" causes boot warnings Qian Cai
2019-08-13 22:35 ` Stephen Boyd
2019-08-13 23:04 ` Tri Vo
2019-08-13 23:10 ` Rafael J. Wysocki
2019-08-14 13:18 ` Qian Cai
2019-08-14 0:35 ` Stephen Boyd [this message]
2019-08-14 7:03 ` Stephen Boyd
2019-08-14 8:40 ` Tony Lindgren
2019-08-14 18:37 ` Tri Vo
2019-08-16 12:17 ` Rafael J. Wysocki
2019-08-16 14:19 ` Stephen Boyd
2019-08-19 9:33 ` Rafael J. Wysocki
2019-08-14 15:19 ` Dmitry Torokhov
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=5d53573f.1c69fb81.a2ac0.65f6@mx.google.com \
--to=swboyd@chromium.org \
--cc=cai@lca.pw \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).