From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH arm 1/1] arm: Use _rcuidle tracepoint to allow use from idle
Date: Tue, 26 Apr 2016 14:08:54 -0700 [thread overview]
Message-ID: <20160426210854.GU3715@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160426165217.5b46eea7@gandalf.local.home>
On Tue, Apr 26, 2016 at 04:52:17PM -0400, Steven Rostedt wrote:
> On Tue, 26 Apr 2016 13:46:15 -0700
> Tony Lindgren <tony@atomide.com> wrote:
>
>
> > [ INFO: suspicious RCU usage. ]
> > 4.6.0-rc5-next-20160426+ #1127 Not tainted
> > -------------------------------
> > include/trace/events/clk.h:45 suspicious rcu_dereference_check() usage!
> >
> > other info that might help us debug this:
> >
> >
> > RCU used illegally from idle CPU!
> > rcu_scheduler_active = 1, debug_locks = 0
> > RCU used illegally from extended quiescent state!
> > 2 locks held by swapper/0/0:
> > #0: (&oh->hwmod_key#30){......}, at: [<c0121afc>] omap_hwmod_enable+0x18/0x44
> > #1: (enable_lock){......}, at: [<c0630684>] clk_enable_lock+0x18/0x124
> >
>
> Hah! I knew that mole would show up.
There do seem to be quite a few candidate moles, don't there?
Thanx, Paul
next prev parent reply other threads:[~2016-04-26 21:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 20:48 [PATCH arm 1/1] arm: Use _rcuidle tracepoint to allow use from idle Paul E. McKenney
2016-04-26 15:00 ` Tony Lindgren
2016-04-26 17:52 ` Paul E. McKenney
2016-04-26 18:29 ` Tony Lindgren
2016-04-26 19:07 ` Paul E. McKenney
2016-04-26 19:39 ` Tony Lindgren
2016-04-26 19:44 ` Steven Rostedt
2016-04-26 19:51 ` Paul E. McKenney
2016-04-26 19:52 ` Steven Rostedt
2016-04-26 20:06 ` Paul E. McKenney
2016-04-26 19:51 ` Tony Lindgren
2016-04-26 20:06 ` Paul E. McKenney
2016-04-26 20:11 ` Paul E. McKenney
2016-04-26 20:25 ` Tony Lindgren
2016-04-26 20:41 ` Paul E. McKenney
2016-04-26 20:46 ` Tony Lindgren
2016-04-26 20:52 ` Steven Rostedt
2016-04-26 21:08 ` Paul E. McKenney [this message]
2016-04-26 21:04 ` Paul E. McKenney
2016-04-26 21:12 ` Tony Lindgren
2016-04-26 21:26 ` Paul E. McKenney
2016-04-26 21:36 ` Tony Lindgren
2016-04-26 20:16 ` Steven Rostedt
2016-04-26 20:36 ` Paul E. McKenney
2016-04-26 19:47 ` Paul E. McKenney
2016-04-26 19:17 ` Steven Rostedt
2016-04-26 19:41 ` Tony Lindgren
2016-04-26 19:42 ` Paul E. McKenney
2016-04-26 19:49 ` Steven Rostedt
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=20160426210854.GU3715@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).