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>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: rcu_prempt stalls / lockup
Date: Thu, 3 Apr 2014 16:01:43 -0400	[thread overview]
Message-ID: <20140403200143.GA8119@redhat.com> (raw)
In-Reply-To: <20140402224840.GA5385@redhat.com>

On Wed, Apr 02, 2014 at 06:48:40PM -0400, Dave Jones wrote:
 
 >  > > >  > 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.
 >  > > 
 >  > > Yep, I would be very surprised if that was related to the grace-period hang.
 >  > 
 >  > Ah, but it could be suppressing later lockdep splats.  So if this can be
 >  > reproduced without xfs, we might get additional information from lockdep.
 > 
 > Hrmph.
 > 
 > $ git bisect bad
 > The merge base 5cb480f6b488128140c940abff3c36f524a334a8 is bad.
 > This means the bug has been fixed between 5cb480f6b488128140c940abff3c36f524a334a8 and [455c6fdbd219161bd09b1165f11699d6d73de11c 62c206bd514600d4d73751ade00dca8e488390a3 e086481baf9d0436bdd6e9b739bfa4a83fb89ef5].
 > 
 > Not sure where to go from here..
 > 
 > The 'good' news is I can reproduce it pretty reliably now.
 > I start my fuzz tester, and immediately do a git diff in my working tree,
 > and then boom..

Even better, now I realise I don't even need my fuzzer in the mix. Just doing
a fair amount of disk io (like a git diff on a dirty tree) will trigger it.

I've tried adding a show_state() call when the stall happens, but another stall
seems to occur before it gets a chance to even dump everything over the usb-serial console.
And of course nothing ever makes it to disk, even though I can sysrq-sync, on the
next reboot systemd has stuffed a bunch of ^@ in the log where the interesting
stuff should be.

Any other ideas ?

	Dave



  reply	other threads:[~2014-04-03 20:02 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
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 [this message]
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=20140403200143.GA8119@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).