From: Fengguang Wu <fengguang.wu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [sched/preempt] INFO: rcu_sched self-detected stall on CPU { 1}
Date: Thu, 6 Feb 2014 19:53:33 +0800 [thread overview]
Message-ID: <20140206115333.GA28544@localhost> (raw)
In-Reply-To: <20140206114635.GA27429@localhost>
On Thu, Feb 06, 2014 at 07:46:35PM +0800, Fengguang Wu wrote:
> On Thu, Feb 06, 2014 at 12:27:31PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 06, 2014 at 05:56:46PM +0800, Fengguang Wu wrote:
> > > Hi Peter,
> > >
> > > We noticed the below RCU stalls which will block the system.
> > > The problem is bisected to
> > >
> > > commit 8cb75e0c4ec9786b81439761eac1d18d4a931af3
> > > Author: Peter Zijlstra <peterz@infradead.org>
> > > AuthorDate: Wed Nov 20 12:22:37 2013 +0100
> > > Commit: Ingo Molnar <mingo@kernel.org>
> > > CommitDate: Mon Jan 13 17:38:55 2014 +0100
> > >
> > > sched/preempt: Fix up missed PREEMPT_NEED_RESCHED folding
> > >
> > > arch/x86/include/asm/mwait.h | 2 +-
> > > include/linux/preempt.h | 15 +++++++++++++++
> > > include/linux/sched.h | 15 +++++++++++++++
> > > kernel/cpu/idle.c | 17 ++++++++++-------
> > > kernel/sched/core.c | 3 +--
> > > 5 files changed, 42 insertions(+), 10 deletions(-)
> > >
> > > [ 85.786775] INFO: rcu_sched self-detected stall on CPU { 1} (t=15000 jiffies g=233 c=232 q=1940)
> >
> > Did the initial kernel contain the below?
>
> Nope, so I was testing some old tip sched/core.. Bisect log is
Peter, I just checked and find no longer showing up in new kernel tests.
So it must have been fixed up. Sorry for the noises!
Regards,
Fengguang
next prev parent reply other threads:[~2014-02-06 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:56 [sched/preempt] INFO: rcu_sched self-detected stall on CPU { 1} Fengguang Wu
2014-02-06 11:27 ` Peter Zijlstra
2014-02-06 11:46 ` Fengguang Wu
2014-02-06 11:53 ` Fengguang Wu [this message]
2014-02-06 12:08 ` Bockholdt Arne
2014-02-06 12:19 ` Peter Zijlstra
2014-02-07 7:06 ` Bockholdt Arne
2014-02-12 6:28 ` Bockholdt Arne
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=20140206115333.GA28544@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).