[ltt-dev] LTTng on ARM target

[madhav chauhan]

Hi Mathiew ,
As you suggested i used ltt-control 0.40.But the same error is coming .Below
i am pasting the complete steps i do after the booting of target.Once i used
to insert the modules some messages i got,Please have a look on them whether
modules inserted properly or not.



#uname -a
Linux localhost 2.6.21.1 #5 PREEMPT Thu Aug 14 20:00:34 IST 2008 armv5tel
unknown

# lsmod
Module                  Size  Used by    Not tainted          /***Before
Module Insertion***/

multipdp               17848  0
fusion                175992  0
g_ether                21144  0
g_serial               23792  0
mhn_u2d                36416  2 g_ether,g_serial
dcm                     7800  1

#  cd /lib/modules/
# ls
dcm.ko                        ltt-probe-fs.ko
fusion.ko                     ltt-probe-kernel.ko
g_ether.ko                    ltt-probe-kernel_arch_arm.ko
g_serial.ko                   ltt-probe-list.ko
gadgetfs.ko                   ltt-probe-mm.ko
gspi.ko                       ltt-probe-net.ko
gspi8686.bin                  ltt-statedump.ko
gspi8xxx.ko                   mhn_optical_joystick.ko
helper_gspi.bin               mhn_u2d.ko
ltt-control.ko                multipdp.ko
ltt-probe-core.ko             vtune_drv.ko

/******Starting Modules insertion********/

# insmod ltt-control.ko
ltt-control init
MADHAV:INSIDE LTT_CONTROL_INITMADHAV SOCKET:-951356928

#  insmod   ltt-probe-core.ko
LTT : Facility core registered with id 0
LTT unable to register probe core_time_heartbeat
LTT unable to register probe core_time_heartbeat_full


# insmod ltt-probe-fs.ko
LTT : Facility fs registered with id 225


#  insmod ltt-probe-kernel.ko
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


#  insmod ltt-probe-kernel_arch_arm.ko
LTT : Facility kernel_arch registered with id 86
LTT unable to register probe kernel_arch_ipc_call


#  insmod ltt-probe-list.ko
LTT : Facility list registered with id 145
LTT unable to register probe list_file_descriptor
LTT unable to register probe list_vm_map
LTT unable to register probe list_interrupt
LTT unable to register probe list_process_state
LTT unable to register probe list_network_ip_interface
LTT unable to register probe list_statedump_end


#  insmod ltt-probe-mm.ko
LTT : Facility mm registered with id 59


# insmod ltt-probe-net.ko
LTT : Facility net registered with id 179
LTT unable to register probe net_socket_call



#  insmod ltt-statedump.ko
LTT : ltt-facility-statedump init

         /*********Listing the modules After Insertion************/

# lsmod
Module                  Size  Used by    Not tainted
ltt_statedump           9144  0
ltt_probe_net           3584  0
ltt_probe_mm            3584  0
ltt_probe_list          3584  0
ltt_probe_kernel_arch_arm     3488  0
ltt_probe_kernel        5728  0
ltt_probe_fs            4896  0
ltt_probe_core          3360  0

ltt_control             3236  0

multipdp               17848  0
fusion                175992  0
g_ether                21144  0
g_serial               23792  0
mhn_u2d                36416  2 g_ether,g_serial
dcm                     7800  1


# lttctl -l /mnt/debugfs/ -t /tmp/trace -n  normal -d -N 1

Linux Trace Toolkit Trace Control 0.40-26042007
Controlling trace : normal
MADHAV:INSIDE LTT_CONTROL
ltt-control bad message length 556 vs. 560

 MADHAV:nlh->nlmsg_len:556 lttctl_peer_msg_t:544 struct nlmsghdr:16

Create Trace Error: Invalid argument




Regards,
Maddy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20080819/eee76ace/attachment-0002.htm>