Re: FTRACE: regression in 31-rc7

From: Steven Rostedt
Date: Thu Aug 27 2009 - 13:03:32 EST

On Thu, 27 Aug 2009, Gregory Haskins wrote:

> Ingo Molnar wrote:
> > * Gregory Haskins <gregory.haskins@xxxxxxxxx> wrote:
> >
> >> Hi Steve,
> >>
> >> I just moved from -rc6 to -rc7, and I noticed that the
> >> function-graph tracer suddenly stopped working properly: I do not
> >> see any output from seeming most things except a handful of
> >> interrupt related events. I currently believe it may be an issue
> >> with tracing modules.
> >>
> >> I haven't had a chance to bisect yet, but I did confirm that
> >> reverting the -rc7 merge restores the previous tracer behavior.
> >> Any help/pointers appreciated.
> >

> Yeah, sorry. I should have provided more detail. Usually I'd hit Steve
> up directly on IRC and he'd point me in the right direction, but he
> wasn't online today. But I guess the "IRC terseness" carried on to the
> mail. ;). I guess I was wondering if anyone else had seen this before
> digging in.

Yeah, my IRC box is my laptop that is overheating. I'm currently backing
it up and I'm going to take it apart today. Hopefully if all goes well,
I'll be back on IRC with a cooler laptop ;-)

> I digress.
> All I was doing was enabling the basic function-graph tracer, enabling
> the tracer, run a test, stopping the tracer, and taking a look at the
> "trace" output by grepping for functions that I knew should have hit.
> In -rc7, grep turns up empty and I can't seem to find evidence that any
> of my code was hit, even though other utilities (like top) indicated my
> code was indeed running (I could see kthreads belonging to my module use
> cpu, for instance). In addition, the test passes so its not like it may
> have skipped over the function I was looking for. Its just not being
> traced for some reason.
> Reverting back to -rc6 and a simple recompile + repeat of the same steps
> indeed restored the behavior that I was accustomed to.
> I noticed that both the output that I could observe, plus the output you
> provide above seem to be core-kernel related functions. I know all the
> traces I was looking for were module related. Therefore, I suspect that
> somehow module code (or at least, my module code) is not being
> instrumented for some reason.

Hmm, so you think something with the modules broke? I can test that out


-- Steve

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at