From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: rcu_prempt stalls / lockup
Date: Fri, 4 Apr 2014 10:06:39 -0700 [thread overview]
Message-ID: <20140404170639.GO4284@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140403223700.GA18353@redhat.com>
On Thu, Apr 03, 2014 at 06:37:00PM -0400, Dave Jones wrote:
> On Thu, Apr 03, 2014 at 05:44:30PM -0400, Dave Jones wrote:
> > On Thu, Apr 03, 2014 at 01:46:56PM -0700, Paul E. McKenney wrote:
> > > git merge anti-fixes
> > >
> > > Then bisect through these reverts.
> > >
> > > I am assuming, perhaps naively, that changes under Documentation and
> > > to torture testing should not be affecting you.
> > >
> > > Does this make sense?
> >
> > I tried reverting every one of those and could still hit it, which
> > seems to indicate the bug is elsewhere, and rcu is just a victim of it.
> > I'm going to start trying to revert the lockdep changes, given this seems
> > to happen after that has warned..
>
> And that was also without any success.
> Tomorrow I'll try a bisect on just arch/x86.
I cannot think of any better debugging strategy at the moment.
Thanx, Paul
prev parent reply other threads:[~2014-04-04 17:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 23:02 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
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 [this message]
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=20140404170639.GO4284@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome