linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: rcu_prempt stalls / lockup
Date: Tue, 1 Apr 2014 14:04:14 -0400	[thread overview]
Message-ID: <20140401180414.GA12326@redhat.com> (raw)
In-Reply-To: <20140401175545.GV4284@linux.vnet.ibm.com>

On Tue, Apr 01, 2014 at 10:55:45AM -0700, Paul E. McKenney wrote:
 > >  > > so kernel space still works like before, but userspace is locked up.
 > >  > 
 > >  > Interesting.  I suspect that if you reverted the rest of this merge
 > >  > window's RCU patches, you would get the same result.
 
Something that occurred to me is that this might be something in the x86 merge
that's just changing timings enough to expose this problem.
At some point this evening, I'll try bisecting it if we don't get any closer.

 > > [ 1953.672735] INFO: Stall ended before state dump start, gp_kthread state: 0x2
 > > [ 2148.608132] INFO: rcu_preempt detected stalls on CPUs/tasks:
 > > [ 2148.609140] 	(detected by 0, t=104027 jiffies, g=47728, c=47727, q=0)
 > > etc etc.
 > 
 > Waiting uninterruptibly.  Presumably blocked on mutex_lock().  But
 > you have CONFIG_PROVE_LOCKING(), so any deadlocks should have been
 > reported.

Lockdep had reported something a little earlier (timestamped at 1108.xxxxxx)
but that's a known false-positive in xfs.

 > Given that you have CONFIG_RCU_TRACE=y, could you please enable the
 > following trace events and dump the trace before things hang?
 > 
 > 	trace_event=rcu:rcu_grace_period,rcu:rcu_grace_period_init
 > 
 > If it is not feasible to dump the trace before things hang, let me
 > know, and I will work out some other diagnostic regime.

I'll give that a shot when I get back in a few hours.

	Dave

  reply	other threads:[~2014-04-01 18:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 23:02 rcu_prempt stalls / lockup Dave Jones
2014-03-31 23:22 ` Paul E. McKenney
2014-03-31 23:35   ` Dave Jones
2014-04-01  0:48     ` Paul E. McKenney
2014-04-01 15:08       ` Dave Jones
2014-04-01 15:30         ` Paul E. McKenney
2014-04-01 17:22           ` Dave Jones
2014-04-01 17:55             ` Paul E. McKenney
2014-04-01 18:04               ` Dave Jones [this message]
2014-04-01 18:32                 ` Paul E. McKenney
2014-04-01 22:16                   ` Dave Jones
2014-04-01 23:18                     ` Paul E. McKenney
2014-04-01 23:31                       ` Dave Jones
2014-04-01 23:57                         ` Paul E. McKenney
2014-04-02  0:07                           ` Dave Jones
2014-04-02 16:20                   ` Paul E. McKenney
2014-04-02 16:23                     ` Dave Jones
2014-04-02 22:48                     ` Dave Jones
2014-04-03 20:01                       ` Dave Jones
2014-04-03 20:46                         ` Paul E. McKenney
2014-04-03 21:44                           ` Dave Jones
2014-04-03 22:37                             ` Dave Jones
2014-04-04 17:06                               ` Paul E. McKenney

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=20140401180414.GA12326@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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).