All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
	Russell King <linux@arm.linux.org.uk>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH arm 1/1] arm: Use _rcuidle tracepoint to allow use from idle
Date: Tue, 26 Apr 2016 11:29:39 -0700	[thread overview]
Message-ID: <20160426182939.GO5995@atomide.com> (raw)
In-Reply-To: <20160426175214.GJ3715@linux.vnet.ibm.com>

* Paul E. McKenney <paulmck@linux.vnet.ibm.com> [160426 10:53]:
> Does the following patch help?

It just changes the output.. See below.

> It is quite possible that there are quite a few more of these.  If this
> is the case, then one way to make the kernel list more of them on a
> given boot is to build with CONFIG_PROVE_RCU_REPEATEDLY=y.

OK

Regards,

Tony

8< ------------------
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000


RCU used illegally from idle CPU!
rcu_scheduler_active = 1, debug_locks = 0
RCU used illegally from extended quiescent state!
no locks held by swapper/1/0.

stack backtrace:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.6.0-rc5-next-20160426+ #1113
Hardware name: Generic OMAP4 (Flattened Device Tree)
[<c0110290>] (unwind_backtrace) from [<c010c3a8>] (show_stack+0x10/0x14)
[<c010c3a8>] (show_stack) from [<c047ff88>] (dump_stack+0xb0/0xe4)
[<c047ff88>] (dump_stack) from [<c012c014>] (pwrdm_set_next_pwrst+0x100/0x1d4)
[<c012c014>] (pwrdm_set_next_pwrst) from [<c0126120>] (omap4_enter_lowpower+0xc8/0x230)
[<c0126120>] (omap4_enter_lowpower) from [<c0126c24>] (omap_enter_idle_coupled+0x6c/0x254)
[<c0126c24>] (omap_enter_idle_coupled) from [<c0601dfc>] (cpuidle_enter_state+0x80/0x3d4)
[<c0601dfc>] (cpuidle_enter_state) from [<c0603d30>] (cpuidle_enter_state_coupled+0x348/0x390)
[<c0603d30>] (cpuidle_enter_state_coupled) from [<c0183d34>] (cpu_startup_entry+0x198/0x3a0)
[<c0183d34>] (cpu_startup_entry) from [<8010162c>] (0x8010162c)
hw-breakpoint: Failed to enable monitor mode on CPU 0.

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
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 11:29:39 -0700	[thread overview]
Message-ID: <20160426182939.GO5995@atomide.com> (raw)
In-Reply-To: <20160426175214.GJ3715@linux.vnet.ibm.com>

* Paul E. McKenney <paulmck@linux.vnet.ibm.com> [160426 10:53]:
> Does the following patch help?

It just changes the output.. See below.

> It is quite possible that there are quite a few more of these.  If this
> is the case, then one way to make the kernel list more of them on a
> given boot is to build with CONFIG_PROVE_RCU_REPEATEDLY=y.

OK

Regards,

Tony

8< ------------------
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000


RCU used illegally from idle CPU!
rcu_scheduler_active = 1, debug_locks = 0
RCU used illegally from extended quiescent state!
no locks held by swapper/1/0.

stack backtrace:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.6.0-rc5-next-20160426+ #1113
Hardware name: Generic OMAP4 (Flattened Device Tree)
[<c0110290>] (unwind_backtrace) from [<c010c3a8>] (show_stack+0x10/0x14)
[<c010c3a8>] (show_stack) from [<c047ff88>] (dump_stack+0xb0/0xe4)
[<c047ff88>] (dump_stack) from [<c012c014>] (pwrdm_set_next_pwrst+0x100/0x1d4)
[<c012c014>] (pwrdm_set_next_pwrst) from [<c0126120>] (omap4_enter_lowpower+0xc8/0x230)
[<c0126120>] (omap4_enter_lowpower) from [<c0126c24>] (omap_enter_idle_coupled+0x6c/0x254)
[<c0126c24>] (omap_enter_idle_coupled) from [<c0601dfc>] (cpuidle_enter_state+0x80/0x3d4)
[<c0601dfc>] (cpuidle_enter_state) from [<c0603d30>] (cpuidle_enter_state_coupled+0x348/0x390)
[<c0603d30>] (cpuidle_enter_state_coupled) from [<c0183d34>] (cpu_startup_entry+0x198/0x3a0)
[<c0183d34>] (cpu_startup_entry) from [<8010162c>] (0x8010162c)
hw-breakpoint: Failed to enable monitor mode on CPU 0.

  reply	other threads:[~2016-04-26 18:29 UTC|newest]

Thread overview: 61+ 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-25 20:48 ` Paul E. McKenney
2016-04-25 20:48 ` Paul E. McKenney
2016-04-26 15:00 ` Tony Lindgren
2016-04-26 15:00   ` Tony Lindgren
2016-04-26 17:52   ` Paul E. McKenney
2016-04-26 17:52     ` Paul E. McKenney
2016-04-26 18:29     ` Tony Lindgren [this message]
2016-04-26 18:29       ` Tony Lindgren
2016-04-26 19:07       ` Paul E. McKenney
2016-04-26 19:07         ` Paul E. McKenney
2016-04-26 19:39         ` Tony Lindgren
2016-04-26 19:39           ` Tony Lindgren
2016-04-26 19:44           ` Steven Rostedt
2016-04-26 19:44             ` Steven Rostedt
2016-04-26 19:51             ` Paul E. McKenney
2016-04-26 19:51               ` Paul E. McKenney
2016-04-26 19:52               ` Steven Rostedt
2016-04-26 19:52                 ` Steven Rostedt
2016-04-26 20:06                 ` Paul E. McKenney
2016-04-26 20:06                   ` Paul E. McKenney
2016-04-26 19:51             ` Tony Lindgren
2016-04-26 19:51               ` Tony Lindgren
2016-04-26 20:06               ` Paul E. McKenney
2016-04-26 20:06                 ` Paul E. McKenney
2016-04-26 20:11                 ` Paul E. McKenney
2016-04-26 20:11                   ` Paul E. McKenney
2016-04-26 20:25                   ` Tony Lindgren
2016-04-26 20:25                     ` Tony Lindgren
2016-04-26 20:25                     ` Tony Lindgren
2016-04-26 20:41                     ` Paul E. McKenney
2016-04-26 20:41                       ` Paul E. McKenney
2016-04-26 20:46                       ` Tony Lindgren
2016-04-26 20:46                         ` Tony Lindgren
2016-04-26 20:52                         ` Steven Rostedt
2016-04-26 20:52                           ` Steven Rostedt
2016-04-26 21:08                           ` Paul E. McKenney
2016-04-26 21:08                             ` Paul E. McKenney
2016-04-26 21:04                         ` Paul E. McKenney
2016-04-26 21:04                           ` Paul E. McKenney
2016-04-26 21:04                           ` Paul E. McKenney
2016-04-26 21:12                           ` Tony Lindgren
2016-04-26 21:12                             ` Tony Lindgren
2016-04-26 21:26                             ` Paul E. McKenney
2016-04-26 21:26                               ` Paul E. McKenney
2016-04-26 21:36                               ` Tony Lindgren
2016-04-26 21:36                                 ` Tony Lindgren
2016-04-26 20:16                 ` Steven Rostedt
2016-04-26 20:16                   ` Steven Rostedt
2016-04-26 20:36                   ` Paul E. McKenney
2016-04-26 20:36                     ` Paul E. McKenney
2016-04-26 19:47           ` Paul E. McKenney
2016-04-26 19:47             ` Paul E. McKenney
2016-04-26 19:17       ` Steven Rostedt
2016-04-26 19:17         ` Steven Rostedt
2016-04-26 19:41         ` Tony Lindgren
2016-04-26 19:41           ` Tony Lindgren
2016-04-26 19:42         ` Paul E. McKenney
2016-04-26 19:42           ` Paul E. McKenney
2016-04-26 19:49           ` Steven Rostedt
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=20160426182939.GO5995@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rostedt@goodmis.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 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.