From: Andi Kleen <andi@firstfloor.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Peter Zijlstra <peterz@infradead.org>,
Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Stephane Eranian <eranian@gmail.com>
Subject: Re: perf related lockdep bug
Date: Thu, 5 Nov 2015 03:46:07 +0100 [thread overview]
Message-ID: <20151105024607.GD3533@two.firstfloor.org> (raw)
In-Reply-To: <20151105005528.GX29027@linux.vnet.ibm.com>
On Wed, Nov 04, 2015 at 04:55:28PM -0800, Paul E. McKenney wrote:
> On Wed, Nov 04, 2015 at 09:58:36PM +0100, Andi Kleen wrote:
> >
> > I tested my perf stress workload with the patch applied on 4.3,
> > unfortunately got a hang again :-/
>
> Any diagnostics, sysrq-T output, or whatever?
The system was dead in the screen saver, no serial console.
I restarted it and may have some more information tomorrow.
The previous hangs were usually timeout on smp_call_function,
so one CPU disappeared.
I'll try the extra hunk you pointed out.
-Andi
next prev parent reply other threads:[~2015-11-05 2:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 5:17 perf related lockdep bug Dave Jones
2015-11-04 10:21 ` Peter Zijlstra
2015-11-04 10:28 ` Peter Zijlstra
2015-11-04 10:50 ` Peter Zijlstra
2015-11-04 13:48 ` Paul E. McKenney
2015-11-04 14:20 ` Peter Zijlstra
2015-11-04 15:34 ` Paul E. McKenney
2015-11-04 15:36 ` Peter Zijlstra
2015-11-04 15:51 ` Paul E. McKenney
2015-11-04 20:58 ` Andi Kleen
2015-11-05 0:55 ` Paul E. McKenney
2015-11-05 1:59 ` Paul E. McKenney
2015-11-05 2:46 ` Andi Kleen [this message]
2015-11-05 14:04 ` Paul E. McKenney
2015-11-11 13:29 ` Paul E. McKenney
2015-11-10 6:39 ` [tip:perf/urgent] perf: Disable IRQs across RCU RS CS that acquires scheduler lock tip-bot for Paul E. McKenney
2015-11-04 14:01 ` perf related lockdep bug Paul E. McKenney
2015-11-04 14:34 ` Peter Zijlstra
2015-11-05 1:57 ` 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=20151105024607.GD3533@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=davej@codemonkey.org.uk \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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.