[ltt-dev] ltt trace files are empty
Dhirender Baliyan
dhir157 at gmail.com
Wed Apr 13 09:15:04 EDT 2011
Hi Srikant,
steps are
# export LTT_DAEMON=/bin/lttd
# mount /mnt/debugfs
# ltt-armall
Connecting all markers
Connecting block bio_backmerge
Connecting block bio_bounce
Connecting block bio_complete
Connecting block bio_frontmerge
Connecting block bio_queue
Connecting block getrq
Connecting block getrq_bio
Connecting block plug
Connecting block remap
Connecting block rq_abort_fs
Connecting block rq_abort_pc
Connecting block rq_complete_fs
Connecting block rq_complete_pc
Connecting block rq_insert_fs
Connecting block rq_insert_pc
Connecting block rq_issue_fs
Connecting block rq_issue_pc
Connecting block rq_requeue_fs
Connecting block rq_requeue_pc
Connecting block sleeprq
Connecting block sleeprq_bio
Connecting block split
Connecting block unplug_io
Connecting block unplug_timer
Connecting fd_state file_descriptor
Connecting fs buffer_wait_end
Connecting fs buffer_wait_start
Connecting fs close
Connecting fs exec
Connecting fs ioctl
Connecting fs llseek
Connecting fs lseek
Connecting fs open
Connecting fs pollfd
Connecting fs pread64
Connecting fs pwrite64
Connecting fs read
Connecting fs readv
Connecting fs select
Connecting fs write
Connecting fs writev
Connecting global_state statedump_end
Connecting input input_event
Connecting ipc call
Connecting ipc msg_create
Connecting ipc sem_create
Connecting ipc shm_create
Connecting irq_state interrupt
Connecting kernel irq_entry
Connecting kernel irq_exit
Connecting kernel kthread_create
Connecting kernel kthread_stop
Connecting kernel kthread_stop_ret
Connecting kernel module_free
Connecting kernel module_load
Connecting kernel page_fault_entry
Connecting kernel page_fault_exit
Connecting kernel page_fault_get_user_entry
Connecting kernel page_fault_get_user_exit
Connecting kernel page_fault_nosem_entry
Connecting kernel page_fault_nosem_exit
Connecting kernel printk
Connecting kernel process_exit
Connecting kernel process_fork
Connecting kernel process_free
Connecting kernel process_wait
Connecting kernel sched_migrate_task
Connecting kernel sched_schedule
Connecting kernel sched_try_wakeup
Connecting kernel sched_wait_task
Connecting kernel sched_wakeup_new_task
Connecting kernel send_signal
Connecting kernel softirq_entry
Connecting kernel softirq_exit
Connecting kernel softirq_raise
Connecting kernel syscall_entry
Connecting kernel syscall_exit
Connecting kernel tasklet_high_entry
Connecting kernel tasklet_high_exit
Connecting kernel tasklet_low_entry
Connecting kernel tasklet_low_exit
Connecting kernel timer_itimer_expired
Connecting kernel timer_itimer_set
Connecting kernel timer_set
Connecting kernel timer_timeout
Connecting kernel timer_update_time
Connecting kernel trap_entry
Connecting kernel trap_exit
Connecting kernel vprintk
Connecting mm huge_page_alloc
Connecting mm huge_page_free
Connecting mm page_alloc
Connecting mm page_free
Connecting mm wait_on_page_end
Connecting mm wait_on_page_start
Connecting module_state list_module
Connecting net dev_receive
Connecting net dev_xmit
Connecting net napi_complete
Connecting net napi_poll
Connecting net napi_schedule
Connecting net socket_call
Connecting net socket_create
Connecting net socket_recvmsg
Connecting net socket_sendmsg
Connecting netif_state del_ifa_ipv4
Connecting netif_state insert_ifa_ipv4
Connecting netif_state insert_ifa_ipv6
Connecting netif_state network_ip_interface
Connecting netif_state network_ipv4_interface
Connecting rcu classic_call_rcu
Connecting rcu classic_call_rcu_bh
Connecting rcu classic_callback
Connecting softirq_state softirq_vec
Connecting task_state process_state
Connecting userspace event
Connecting vm_state vm_map
Connecting high-rate markers to tap
# lttctl -C -w /tmp/trace1 trace1
Linux Trace Toolkit Trace Control 0.64-14012009
Controlling trace : trace1
lttctl: Creating trace
lttctl: Forking lttd
Linux Trace Toolkit Trace Daemon 0.64-14012009
Reading from debugfs directory : /mnt/debugfs/ltt/trace1
Writing to trace directory : /tmp/trace1
lttctl: Starting trace
*then i run my test*
#./ltttest
parent pid:94
1:Hello
2:Hello
1:World!
2:World!
# lttctl -D trace1
Linux Trace Toolkit Trace Control 0.64-14012009
Controlling trace : trace1
lttctl: Pausing trace
lttctl: Destroying trace
#ltt-disarmall
# lttv -m textDump -t /tmp/trace1
The input data file /var/tmp/trace1/metadata_0 does not contain a trace
The input data file /var/tmp/trace1/block_0 does not contain a trace
The input data file /var/tmp/trace1/fd_state_0 does not contain a trace
The input data file /var/tmp/trace1/fs_0 does not contain a trace
The input data file /var/tmp/trace1/global_state_0 does not contain a trace
The input data file /var/tmp/trace1/input_0 does not contain a trace
The input data file /var/tmp/trace1/ipc_0 does not contain a trace
The input data file /var/tmp/trace1/irq_state_0 does not contain a trace
**
ERROR:tracefile.c:1355:map_block: assertion failed: (block_num <
tf->num_blocks)
/bin/lttv: line 15: 101 Aborted $0.real $*
# ls -l /tmp/trace1/
-rwxr-xr-x 1 root root 0 Jan 1 00:04 block_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 fd_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 fs_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 global_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 input_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 ipc_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 irq_state_0
-rwxr-xr-x 1 root root 634880 Jan 1 00:04 kernel_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 metadata_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 mm_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 module_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 net_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 netif_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 rcu_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 softirq_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 task_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 userspace_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 vm_state_0
i am attching /tmp/trace1 and /mnt/debugfs
still am not getting traces through lttv
Regards
Dhirender
On Wed, Apr 13, 2011 at 3:53 PM, Srikanth Krishnakar
<skrishnakar at gmail.com>wrote:
> Dhirendar,
>
> You just connected the markers, where are the further steps ?
>
> I mean :
>
> 1. ltt-armall
> 2. lttctl -C -w /tmp/trace1 trace1
>
> <Run your tests here, If you have any >
>
> 3. lttctl -D trace1
> 4. ltt-disarmall
> 5. lttv -m textDump -t /tmp/trace1
>
>
> -skrishnakar
>
>
>
> On 04/13/2011 02:38 PM, Dhirender Baliyan wrote:
>
>
>
>
> Hi
>
> I am using
> 1) lttng 2.6.28.4
> 2)lttctl 0.64
> 3) lttv-0.12.10
>
> cross compiled it for mips
>
> my config option are CONFIG_LTT=y
> CONFIG_LTT_FILTER=y
> CONFIG_LTT_TRACEPROBES=y
> # CONFIG_HAVE_LTT_DUMP_TABLES is not set
> CONFIG_LTT_RELAY_ALLOC=y
> CONFIG_LTT_RELAY=y
> # CONFIG_LTT_RELAY_LOCKED is not set
> # CONFIG_LTT_RELAY_CHECK_RANDOM_ACCESS is not set
> CONFIG_LTT_SERIALIZE=y
> CONFIG_LTT_MARKER_CONTROL=y
> CONFIG_LTT_TRACER=y
> CONFIG_LTT_ALIGNMENT=y
> CONFIG_LTT_DEBUG_EVENT_SIZE=y
> CONFIG_LTT_USERSPACE_EVENT=y
> CONFIG_LTT_VMCORE=y
> CONFIG_LTT_NETLINK_CONTROL=y
> CONFIG_LTT_TRACE_CONTROL=y
> CONFIG_LTT_STATEDUMP=y
>
> now
> ltt-armall
> lttctl os running fine
>
> but when i do
> lttv -m textDump -t /tmp/trace1
> The input data file /var/tmp/trace1/metadata_0 does not contain a trace
> The input data file /var/tmp/trace1/block_0 does not contain a trace
> The input data file /var/tmp/trace1/fd_state_0 does not contain a trace
> The input data file /var/tmp/trace1/fs_0 does not contain a trace
> The input data file /var/tmp/trace1/global_state_0 does not contain a trace
> The input data file /var/tmp/trace1/input_0 does not contain a trace
> The input data file /var/tmp/trace1/ipc_0 does not contain a trace
> The input data file /var/tmp/trace1/irq_state_0 does not contain a trace
> **
> ERROR:tracefile.c:1355:map_block: assertion failed: (block_num <
> tf->num_blocks)
> /bin/lttv: line 15: 100 Aborted $0.real $*
>
> this output is coming
> so i checked /tmp/trace1 file , then i found the files are having 0 size
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 block_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 fd_state_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 fs_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 global_state_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 input_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 ipc_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 irq_state_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 kernel_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 metadata_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 mm_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 module_state_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 net_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 netif_state_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 rcu_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 softirq_state_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 task_state_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 userspace_0
> -rwxr-xr-x 1 root root 0 Jan 1 00:07 vm_state_0
>
> I am not getting why this is coming.
> Please help
> Thanks in advance
>
> Regards
> Dhiren
>
>
> _______________________________________________
> ltt-dev mailing listltt-dev at lists.casi.polymtl.cahttp://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110413/94671c0d/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: trace1.zip
Type: application/zip
Size: 215523 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110413/94671c0d/attachment-0006.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debugfs.zip
Type: application/zip
Size: 5977 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110413/94671c0d/attachment-0007.zip>
More information about the lttng-dev
mailing list