mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Pratyush Anand <panand@redhat.com>
Cc: open list <linux-kernel@vger.kernel.org>
Subject: Re: Query: rcu_sched detected stalls with function_graph tracer
Date: Wed, 2 Aug 2017 07:56:50 -0400	[thread overview]
Message-ID: <20170802075650.7dab7586@gandalf.local.home> (raw)
In-Reply-To: <cfae823d-1154-f3cb-8281-842fe7fc94b9@redhat.com>

On Wed, 2 Aug 2017 12:02:21 +0530
Pratyush Anand <panand@redhat.com> wrote:

> Hi Steve,
> 
> I am using a 3.10 based kernel, and when I enable function_graph with one 
> particular x86_64 machine, I encounter rcu_sched stall.
> 
> echo function_graph > /sys/kernel/debug/tracing/current_tracer
> echo 1 > /sys/kernel/debug/tracing/tracing_on
> 
> If I use 4.13-rc2, then its better, but still goes for it after a bit of 
> stressing with stressng.
> 
> It looks like that this behavior should be expected with a loaded system (like 
> that of ftrace-graph tracing for all available function) which can cause RCU 
> stall warning. But,I am not an expert. So, whats your opinion on it?
> 
> I tried to bisect and there was no particular function which can cause this. 
> It looked like that when we had more than 5000 functions in set_ftrace_filter, 
> we start getting such warnings. Tried by putting some most  hit functions like 
> spin_lock* etc in set_ftrace_notrace. Still, no help.  Do you have some 
> suggestion for further debugging pointers?
> 
> log with 3.10 based kernel

Can you send me the config. I'm also guessing that this is a RHEL 3.10
based kernel (which means it's not 3.10 at all).

-- Steve

      reply	other threads:[~2017-08-02 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  6:32 Pratyush Anand
2017-08-02 11:56 ` Steven Rostedt [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=20170802075650.7dab7586@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=panand@redhat.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

all inboxes | Powered by JetHome®