From: Peter Zijlstra <peterz@infradead.org>
To: Ross Green <rgkernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com
Subject: Re: rcu_preempt self-detected stall on CPU from 4.4-rc4, since 3.17
Date: Fri, 11 Dec 2015 12:30:51 +0100 [thread overview]
Message-ID: <20151211113051.GH6356@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CANfgCY2bSyw9n9tYZW46yRHXM-fF+XqobVOjjE_uOWcPaUWHCA@mail.gmail.com>
On Fri, Dec 11, 2015 at 10:17:33PM +1100, Ross Green wrote:
> I have been getting these stalls in kernels going back to 3.17.
>
> This stall occurs usually under light load but often requires several
> days to show itself. I have not found any simple way to trigger the
> stall. Indeed heavy workloads seems not to show the fault.
>
> Anyone have any thoughts here?
see lkml.kernel.org/r/564F3DCA.1080907@arm.com
next prev parent reply other threads:[~2015-12-11 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 11:17 rcu_preempt self-detected stall on CPU from 4.4-rc4, since 3.17 Ross Green
2015-12-11 11:30 ` Peter Zijlstra [this message]
2016-01-03 5:29 ` Ross Green
2016-01-03 6:17 ` Paul E. McKenney
2016-01-03 8:27 ` Ross Green
2016-01-03 18:15 ` Paul E. McKenney
2016-01-03 22:00 ` Ross Green
2016-01-04 14:21 ` Ross Green
2016-01-06 23:10 ` Ross Green
2016-01-08 18:35 ` Paul E. McKenney
2016-01-14 5:39 ` Ross Green
2016-01-16 0:39 ` 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=20151211113051.GH6356@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rgkernel@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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