From: Dave Jones <davej@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: at kernel/trace/ftrace.c:1605 __ftrace_hash_rec_update.part.37+0x20a/0x240()
Date: Mon, 10 Jun 2013 20:37:12 -0400 [thread overview]
Message-ID: <20130611003712.GA9537@redhat.com> (raw)
In-Reply-To: <1370910794.9844.150.camel@gandalf.local.home>
On Mon, Jun 10, 2013 at 08:33:14PM -0400, Steven Rostedt wrote:
> On Mon, 2013-06-10 at 19:48 -0400, Dave Jones wrote:
> > 3.10-rc5 + the two patches referenced in the RCU thread from earlier.
> >
> > Dave
> >
> > [ 2313.381283] WARNING: at kernel/trace/ftrace.c:1605 __ftrace_hash_rec_update.part.37+0x20a/0x240()
>
> Grumble,
>
> Somehow the list of functions that perf enabled got out of sync with
> what ftrace had. When perf disabled its list of functions from ftrace,
> perf thought it had a function enabled that wasn't and ftrace cried
> about that.
>
> What does 'trinity-child2' do?
Same as all the other child processes. Random syscalls, semi-intelligent args.
> and is this reproducible?
I'm sure I'll hit it again eventually. The This one looks tricky because
the trace isn't a syscall that I can go hammer on, it's happening
at process exit time.
Dave
next prev parent reply other threads:[~2013-06-11 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 23:48 WARNING: at kernel/trace/ftrace.c:1605 __ftrace_hash_rec_update.part.37+0x20a/0x240() Dave Jones
2013-06-11 0:33 ` Steven Rostedt
2013-06-11 0:37 ` Dave Jones [this message]
2013-06-28 20:45 ` Dave Jones
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=20130611003712.GA9537@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.