Re: linux 2.6.22.7

karthikeyan.s <[email protected]> Wed, 26 Dec 2007 17:50:19 +0530
Newsgroups gmane.linux.kernel.tracing
Message-ID <[email protected]>
Hi,
Had some doubts in your comments.

>> ** (process:25057): WARNING **: Unknown facility 145 (0x91) in tracefile
>> /control/interrupts
>>
>> ** (process:25057): WARNING **: Unknown facility 211 (0xd3) in tracefile
>> /cpu
>>
>> ** ERROR **: file event.c: line 86 (ltt_event_facility): assertion
failed:
>> (facility->exists)

>Could be caused by the "unable to register probe" messages, caused by
>incorrect CONFIG_SMP ifdefs in probes.

I did not get what you mean by CONFIG_SMP ifdefs in probes. There is no such
thing in those files(ltt/probes/).

I have been trying root cause this. I noticed that the viewer gets the
facility id from an offset in the trace file. And the warning comes because
the viewer does not recognise the event (the value range for the events is 0
to 5 (or 4) and it gets 168(0xa8) for facility net) Could it be that the
problem is there in lttv( it got the wrong offsets of the trace data ? ). Or
can lttv error be ruled out and just focus on the kernel side? I also looked
at 0.9.6 and i did not find CONFIG_SMP ifdefs.

And yes, what happens when the CONFIG_SMP ifdef is incorrect?

I am not bothered much about the buffer overflow issue right now, but i
think i can take care of it by allocating more buffers.

_______________________________________________
Ltt-dev mailing list
[email protected]
http://listserv.shafik.org/mailman/listinfo/ltt-dev