Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1550967

Re: INFO: rcu_sched self-detected stall on CPU

From "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Newsgroups linux.kernel
Subject Re: INFO: rcu_sched self-detected stall on CPU
Date 2017-01-04 17:20 +0100
Message-ID <sVWsa-72d-43@gated-at.bofh.it> (permalink)
References <sVQwp-2U6-5@gated-at.bofh.it> <sVU70-5lr-39@gated-at.bofh.it> <sVUA2-5Oz-29@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Jan 04, 2017 at 09:16:31AM -0500, Steven Rostedt wrote:
> On Wed, 4 Jan 2017 05:46:08 -0800
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> 
> > I suggest enabling tracing for timers with a goal of working out why
> > the rcu_sched task is not being awakened regularly -- during a grace
> > period, it should be awakened every three jiffies or so (depending on
> > the value of HZ).
> 
> Perhaps enable events for rcu, sched and irqs as well?

Good point -- but you will need to build with CONFIG_RCU_TRACE=y
to get most of the RCU events.

							Thanx, Paul

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: INFO: rcu_sched self-detected stall on CPU Steven Rostedt <rostedt@goodmis.org> - 2017-01-04 15:20 +0100
  Re: INFO: rcu_sched self-detected stall on CPU Enrico Mioso <mrkiko.rs@gmail.com> - 2017-01-04 16:50 +0100
  Re: INFO: rcu_sched self-detected stall on CPU "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2017-01-04 17:20 +0100
    Re: INFO: rcu_sched self-detected stall on CPU Enrico Mioso <mrkiko.rs@gmail.com> - 2017-01-05 19:40 +0100
      Re: INFO: rcu_sched self-detected stall on CPU "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2017-01-06 08:50 +0100

csiph-web