Re: linux 2.6.22.7
karthikeyan.s <[email protected]> Wed, 19 Dec 2007 18:16:34 +0530
| Newsgroups | gmane.linux.kernel.tracing |
|---|---|
| Message-ID | <[email protected]> |
Hi, yet to get a reply but adding on what all i tried. I looked at http://listserv.shafik.org/pipermail/ltt-dev/2006-July/001619.html as i am also trying to get it run in a target. and tried creating the header files using genevent only for arch_arm.xml. But on trying to build the kernel i get some undefined references which are mentioned below: 1) ltt_get_index_from_facility_kernel_arch. 2) ltt_facility_kernel_arch_E2D841CD. Where are these function defined. Am i using a wrong version of genevent? Thanks, Karthik On 12/18/07, karthikeyan. s <[email protected]> wrote: > > Hi again, > Followed the instructions as such from quickstart guide. By the way, i > have an arm core here. > > ltt-control-0.43-10082007 > lttv --> 0.8.82 > lttng patch --> 0.9.5 > > Here is the message form dmesg > LTT : ltt-facilities init > LTT : Facility kernel_arch registered with id 86 > LTT : Facility kernel registered with id 211 > LTT unable to register probe kernel_sched_wait_task > LTT unable to register probe kernel_sched_migrate_task > LTT : Facility list registered with id 145 > LTT : ltt-relay init > ltt-control init > LTT : ltt-facility-statedump init > > ltt-control ltt_control_input > ltt_control : trace trace > Creating trace trace > ltt-control ltt_control_input > ltt_control : trace trace > Start tracing trace > Dumping facility kernel_arch > Dumping facility list > Dumping facility kernel > ltt_statedump_start > do_ltt_statedump > do_ltt_statedump end > ---- > ltt-control ltt_control_input > ltt_control : trace trace > Stop tracing trace > ltt-control ltt_control_input > ltt_control : trace trace > Destroying trace trace > LTT : cpu : 22954 events lost in cpu channel (cpu 0). > -------- > When i run textdump > > lttv -m textDump -t /tmp/trace > > I get > --- > ** (process:25057): WARNING **: Unknown facility 145 (0x91) in tracefile > /control/network > > ** (process:25057): WARNING **: Unknown facility 145 (0x91) in tracefile > /control/processes > > ** (process:25057): WARNING **: Unknown facility 211 (0xd3) in tracefile > /control/modules > > ** (process:25057): WARNING **: Unknown facility 145 (0x91) in tracefile > /control/interrupts > > ** (process:25057): WARNING **: Unknown facility 211 (0xd3) in tracefile > /cpu > Trace set contains 1 traces > > > ** (process:25057): WARNING **: Unknown facility 145 (0x91) in tracefile > /control/network > > ** (process:25057): WARNING **: Unknown facility 145 (0x91) in tracefile > /control/processes > > ** (process:25057): WARNING **: Unknown facility 211 (0xd3) in tracefile > /control/modules > > ** (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) > aborting... > /usr/local/bin/lttv: line 15: 25057 Aborted $0.real $* > ------ > > Any help is appreciated. > > Thanks, > karthik > > On 12/17/07, karthikeyan. s <[email protected]> wrote: > > > > > > Hi mathieu, > > Thanks for the reply. > > > > I patched the 2.6.22.7 kernel with 2.6.21 patch.Patching was not an > > issue but getting it to run is a problem. And i did not have to get any file > > from the 2.6.22-mm* patches (most probable cause? ). > > > > Should I take a 2.6.22 or 2.6.23 patch and sort things out or use 2.6.21and go ahead? > > > > Thanks again! > > karthik > > > > > > On Nov 16, 2007 7:36 PM, Mathieu Desnoyers <[email protected]> > > wrote: > > > > > * karthikeyan.s ([email protected]) wrote: > > > > Hi, > > > > I am required to use 2.6.22.7 kernel. > > > > > > > > There are a bunch of patches available. But none seem to be for the > > > mainline > > > > kernel. > > > > > > > > Can you please suggest which patch to use, as i have already > > > suffered a lot > > > > on using a patch and reverting back a number of times > > > > > > > > 2.6.22-rc2-mm1 > > > > 2.6.22-rc4-mm2 > > > > 2.6.22.1-rt4 > > > > 2.6.22-rc2-mm1 > > > > > > > > > > There is no LTTng specifically for 2.6.22, a port will be needed. > > > (which > > > means fixing the rejects, grabbing some files from the -mm patches...) > > > > > > > > > Mathieu > > > > > > > Thanks! > > > > -karthik > > > > > > > _______________________________________________ > > > > Ltt-dev mailing list > > > > [email protected] > > > > http://listserv.shafik.org/mailman/listinfo/ltt-dev > > > > > > > > > -- > > > Mathieu Desnoyers > > > Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal > > > OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE > > > 9A68 > > > > > > > > > > > -- > > --- > > S. Karthikeyan | +919980814745 > > --- > > > > > -- > --- > S. Karthikeyan | +919980814745 > --- -- --- S. Karthikeyan | +919980814745 --- _______________________________________________ Ltt-dev mailing list [email protected] http://listserv.shafik.org/mailman/listinfo/ltt-dev