Messages in this thread | | | Date | Mon, 10 Jun 2013 20:37:12 -0400 | From | Dave Jones <> | Subject | Re: WARNING: at kernel/trace/ftrace.c:1605 __ftrace_hash_rec_update.part.37+0x20a/0x240() |
| |
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
| |