[ltt-dev] Using LTTng on DA8xx Target
Mathieu Desnoyers
compudj at krystal.dyndns.org
Wed Nov 12 12:18:31 EST 2008
* saumya agarwal (cmks2002 at gmail.com) wrote:
> Hi,
>
> I have installed LTTV 0.8.72 on my host machine.
> and did following after booting the target board, please see the logs below:
>
> U-Boot > bootm
> ## Booting kernel from Legacy Image at c0700000 ...
> Image Name: Linux-2.6.18_pro500
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 1989268 Bytes = 1.9 MB
> Load Address: c0008000
> Entry Point: c0008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing
> Linux.............................................................
> ...................................................................... done,
> boo
> ting the kernel.
> Linux version 2.6.18_pro500 (root at LSP2x-UCLIBC) (gcc version 4.2.0
> (MontaVista 4
> .2.0-16.0.38.0802273 2008-10-11)) #1 PREEMPT Wed Nov 12 11:39:24 IST 2008
> CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
> Machine: DaVinci DA8XX EVM
> Memory policy: ECC disabled, Data cache writethrough
> DaVinci DA0800 variant 0x0
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> Built 1 zonelists. Total pages: 32768
> Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/nfs rw
> nfsroot=10
> .24.241.126:/opt/mvl_pro50/uclibc/target,nolock mem=128M
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> Clock event device timer0_0 configured with caps set: 03
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 128MB = 128MB total
> Memory: 125568KB available (3449K code, 647K data, 152K init)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> DaVinci: 128 gpio irqs
> Generic PHY: Registered new driver
> SCSI subsystem initialized
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 4096 (order: 2, 16384 bytes)
> TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
> TCP: Hash tables configured (established 4096 bind 2048)
> TCP reno registered
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> squashfs: version 3.1 (2006/08/19) Phillip Lougher
> NTFS driver 2.1.27 [Flags: R/W].
> JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
> yaffs Nov 12 2008 11:35:58 Installing.
> JFS: nTxBlock = 981, nTxLock = 7853
> SGI XFS with no debug enabled
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> LTT : ltt-facilities init
> LTT : ltt-facility-core init in kernel
> LTT : ltt-relay init
> DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec
> Serial: 8250/16550 driver $Revision: 1.90 $ 3 ports, IRQ sharing disabled
> serial8250.0: ttyS0 at MMIO map 0x1c42000 mem 0xfec42000 (irq = 25) is a
> 16550A
> serial8250.0: ttyS1 at MMIO map 0x1c20400 mem 0xfed0c000 (irq = 53) is a
> 16550A
> serial8250.0: ttyS2 at MMIO map 0x1d0d000 mem 0xfed0d000 (irq = 61) is a
> 16550A
> RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
> netconsole: not configured, aborting
> Davinci EMAC MII Bus: probed
> MAC address is 00:0e:99:02:f0:30
> TI DaVinci EMAC Linux version updated 4.0
> i2c /dev entries driver
> physmap platform flash device: 01000000 at 60000000
> physmap-flash physmap-flash.0: map_probe failed
> nand_davinci nand_davinci.0: Using 4-bit hardware ECC
> No NAND device found!!!
> nand_davinci nand_davinci.0: no nand device detected
> Creating 3 MTD partitions on "Windbond spi nand flash":
> 0x00000000-0x00020000 : "U-Boot"
> 0x00020000-0x00024000 : "U-Boot Environment"
> 0x00024000-0x00400000 : "Linux"
> dm_spi.0: davinci SPI Controller driver at 0xfec41000 (irq = 20) use_dma=1
> dm_spi.1: davinci SPI Controller driver at 0xfee12000 (irq = 56) use_dma=1
> ohci ohci.0: DA8xx OHCI
> ohci ohci.0: new USB bus registered, assigned bus number 1
> ohci ohci.0: irq 59, io mem 0x01e25000
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
> Initializing USB Mass Storage driver...
> usbcore: registered new driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new driver libusual
> musb_hdrc: version 6.0, cppi4.1-dma, host, debug=0
> Waiting for PHY clock good...
> musb_hdrc: USB Host mode controller at c8900000 using DMA, IRQ 58
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 1 port detected
> mice: PS/2 mouse device common for all mice
> rtc-da8xx rtc-da8xx.0: rtc intf: proc
> rtc-da8xx rtc-da8xx.0: rtc intf: dev (254:0)
> rtc-da8xx rtc-da8xx.0: rtc core: registered rtc-da8xx as rtc0
> rtc-da8xx rtc-da8xx.0: TI DA8xx Real Time Clock driver.
> IPv4 over IPv4 tunneling driver
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> rtc-da8xx rtc-da8xx.0: setting the system clock to 2000-01-05 00:00:46
> (94703044
> 6)
> Time: timer0_1 clocksource has been installed.
> Clock event device timer0_0 configured with caps set: 08
> Switched to high resolution mode on CPU 0
> usb 2-1: new high speed USB device using musb_hdrc and address 2
> usb 2-1: configuration #1 chosen from 1 choice
> scsi0 : SCSI emulation for USB Mass Storage devices
> Sending DHCP and RARP requests .., OK
> IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.24.241.69
> IP-Config: Complete:
> device=eth0, addr=10.24.241.69, mask=255.255.255.0, gw=10.24.241.1,
> host=10.24.241.69, domain=india.ext.ti.com, nis-domain=(none),
> bootserver=0.0.0.0, rootserver=10.24.241.126, rootpath=
> Looking up port of RPC 100003/2 on 10.24.241.126
> Looking up port of RPC 100005/1 on 10.24.241.126
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 152K
> INIT: version 2.86 booting
> Vendor: Generic Model: STORAGE DEVICE Rev: 9339
> Type: Direct-Access ANSI SCSI revision: 00
> SCSI device sda: 494080 512-byte hdwr sectors (253 MB)
> sda: Write Protect is off
> sda: assuming drive cache: write through
> SCSI device sda: 494080 512-byte hdwr sectors (253 MB)
> sda: Write Protect is off
> sda: assuming drive cache: write through
> sda: sda1
> sd 0:0:0:0: Attached scsi removable disk sda
> sd 0:0:0:0: Attached scsi generic sg0 type 0
> Starting the hotplug events dispatcher: udevd.
> Synthesizing the initial hotplug events...done.
> Waiting for /dev to be fully populated...done.
> Activating swap...done.
> Remounting root filesystem...done.
> Checking all file systems: fsck
> fsck 1.40 (29-Jun-2007)
> Mounting local filesystems: mount debugfs on /mnt/debugfs type debugfs (rw)
> umount.nfs: /dev/root: not found or not mounted
> /etc/network/options is deprecated.
> Setting up IP spoofing protection: rp_filter done.
> Disabling IPv4 packet forwarding: done.
> Disabling TCP/IP Explicit Congestion Notification: done.
> Starting network interfaces: done.
> Starting portmap daemon....
> Mounting remote filesystems...: .
> Cleaning: /tmp /var/lock /var/run done.
> Updating /etc/motd...done.
> INIT: Entering runlevel: 3
> Starting system log daemon: syslogd klogd.
> Starting NFS common utilities: statd.
> Starting internet superserver: inetd.
> Starting OpenBSD Secure Shell server: sshd.
>
> MontaVista(R) Linux(R) Professional Edition 5.0.0 (0802297)
>
> 10.24.241.69 login: root
> Last login: Tue Jan 4 23:59:09 2000 on console
> Linux 10.24.241.69 2.6.18_pro500 #1 PREEMPT Wed Nov 12 11:39:24 IST 2008
> armv5te
> jl GNU/Linux
> root at 10.24.241.69:~# cd /home/saumya/lsp2.2/02/
> PSP_02.20.00.02/ montavista/ testing/ uninstall
>
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# ls
> ltt-control.ko ltt-facility-loader-statedump.ko
> ltt-facility-loader-fs.ko ltt-facility-loader-timer.ko
> ltt-facility-loader-fs_data.ko ltt-probe-arm.ko
> ltt-facility-loader-ipc.ko ltt-probe-fs.ko
> ltt-facility-loader-kernel.ko ltt-probe-ipc.ko
> ltt-facility-loader-kernel_arch_arm.ko ltt-probe-kernel.ko
> ltt-facility-loader-memory.ko ltt-probe-list.ko
> ltt-facility-loader-network.ko ltt-probe-mm.ko
> ltt-facility-loader-network_ip_interface.ko ltt-probe-net.ko
> ltt-facility-loader-process.ko ltt-statedump.ko
> ltt-facility-loader-socket.ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod ltt-tracer.ko
> .ko
> insmod ltt-facility-loader-process.ko
> insmod ltt-facility-loader-socket.ko
> insmod ltt-facility-loader-statedump.ko
> insmod ltt-facility-loader-timer.ko
> insmod ltt-probe-arm.ko
> insmod ltt-probe-fs.ko
> insmod ltt-probe-ipc.ko
> insmod ltt-proinsmod: can't read 'ltt-tracer.ko': No such file or directory
> be-kernel.ko
> insmod ltt-probe-list.ko
> insmod ltt-probe-net.ko
> insmod ltt-relay.ko
> insmod ltt-statedump.koroot at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng#
> i
> nsmod ltt-control.ko
> ltt-control init
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-fs.ko
> LTT : ltt-facility-fs init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-fs_data.ko
> LTT : ltt-facility-fs_data init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-ipc.ko
> LTT : ltt-facility-ipc init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-kernel.ko
> LTT : ltt-facility-kernel init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-kernel_arch_arm.ko
> LTT : ltt-facility-kernel_arch init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-memory.ko
> LTT : ltt-facility-memory init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-network.ko
> LTT : ltt-facility-network init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-network_ip_interface.ko
> LTT : ltt-facility-network_ip_interface init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-process.ko
> LTT : ltt-facility-process init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-socket.ko
> LTT : ltt-facility-socket init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-statedump.ko
> LTT : ltt-facility-statedump init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-facility-load
> er-timer.ko
> LTT : ltt-facility-timer init in kernel
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-probe-arm.ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-probe-fs.ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-probe-ipc.ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-probe-kernel.
> ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-probe-list.ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-probe-list.ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-probe-net.ko
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod ltt-relay.ko
> insmod: can't read 'ltt-relay.ko': No such file or directory
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# insmod
> ltt-statedump.ko
> LTT : ltt-facility-statedump init
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# lsmod
> Module Size Used by
> ltt_statedump 10484 0
> ltt_probe_net 7136 0
> ltt_probe_list 2560 0
> ltt_probe_kernel 19200 0
> ltt_probe_ipc 3520 0
> ltt_probe_fs 13088 0
> ltt_probe_arm 5632 0
> ltt_facility_loader_timer 2408 1 ltt_probe_kernel
> ltt_facility_loader_statedump 2472 2 ltt_statedump,ltt_probe_list
> ltt_facility_loader_socket 2440 1 ltt_probe_net
> ltt_facility_loader_process 2440 1 ltt_probe_kernel
> ltt_facility_loader_network_ip_interface 2664 1 ltt_probe_net
> ltt_facility_loader_network 2440 1 ltt_probe_net
> ltt_facility_loader_memory 2440 1 ltt_probe_arm
> ltt_facility_loader_kernel_arch_arm 2504 1 ltt_probe_arm
> ltt_facility_loader_kernel 2440 2 ltt_probe_kernel,ltt_probe_arm
> ltt_facility_loader_ipc 2376 2 ltt_probe_ipc,ltt_probe_arm
> ltt_facility_loader_fs_data 2440 1 ltt_probe_fs
> ltt_facility_loader_fs 2376 1 ltt_probe_fs
> ltt_control 2724 0
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# ls /usr/bin/ltt
> ltt-load lttctl lttv lttv.real
> ltt-unload lttd lttv-gui
ltt-load seems to be a script packaged by your disto vendor to do all
the insmods.
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# lttctl -n trace -d
> -l /mnt/debugfs/ltt -t /tmp/trace
> Linux Trace Toolkit Trace Controltt_control : trace trace
> l 0.30-09112006
>
> Controlling trace : trace
>
> Linux Trace Toolkit Trace Daemon 0.30-09112006
>
> Reading from debugfs directory : /mnt/debugfs/ltt/trace
> Writing to trace directory : /tmp/trace
>
> Creating supplementary trace files
> Appending facility file timer.xml
> Appending facility file kernel_arch_ppc.xml
> Appending facility file kernel_arch_c2.xml
> Appending facility file kernel_arch_x86_64.xml
> Appending facility file network.xml
> Appending facility file socket.xml
> Appending facility file locking.xml
> Appending facility file kernel_arch_mips.xml
> Appending facility file fs_data.xml
> Appending facility file network_ip_interface.xml
> Appending facility file core.xml
> Appending facility file memory.xml
> Appendiltt_control : trace trace
> ng facility file fs.xml
> Appending facility file user_generic.xml
> Appending facility file stack.xml
> Appending facility file statedump.xml
> Appending facility file kernel_arch_i386.xml
> Appending facility file kernel_arch_arm.xml
> Appending facility file ipc.xml
> Appending facility file kernel_arch_powerpc.xml
> Appending facility file kernel.xml
> Appending facility file process.xml
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# lttctl -n trace -R
> ltt_control : trace trace
> Linux Trace Toolkit Trace Control 0.30-09112006
>
> Controlling trace : trace
>
> ltt_control : trace trace
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# lttv -m textDump -t
> /tmp/trace -o logdump.txt
>
> ** ERROR **: cannot open file dump.txt
> aborting...
> /usr/bin/lttv: line 15: 921 Trace/breakpoint trap $0.real $*
Hrm, is the -o directory on a read-only filesystem ?
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# lttv -m textDump -t
> /tmp/trace -o /tmp/trace/dump.txt
>
> ** ERROR **: file ../../../lttv/lttv/state.c: line 2248 (process_fork):
> assertion failed: (0)
> aborting...
> /usr/bin/lttv: line 15: 923 Trace/breakpoint trap $0.real $*
Hrm, looks like you have either an unsynchronized clock source (very
unlikely, given this seems to be a UP system) or non-matching
kernel/lttv versions.
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng#
>
>
>
>
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng# dmesg
> Linux version 2.6.18_pro500 (root at LSP2x-UCLIBC) (gcc version 4.2.0
> (MontaVista 4
> .2.0-16.0.38.0802273 2008-10-11)) #1 PREEMPT Wed Nov 12 11:39:24 IST 2008
> CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
> Machine: DaVinci DA8XX EVM
> Memory policy: ECC disabled, Data cache writethrough
> On node 0 totalpages: 32768
> DMA zone: 32768 pages, LIFO batch:7
> DaVinci DA0800 variant 0x0
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> Built 1 zonelists. Total pages: 32768
> Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/nfs rw
> nfsroot=10
> .24.241.126:/opt/mvl_pro50/uclibc/target,nolock mem=128M
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> Clock event device timer0_0 configured with caps set: 03
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 128MB = 128MB total
> Memory: 125568KB available (3449K code, 647K data, 152K init)
> Calibrating delay loop... 149.50 BogoMIPS (lpj=747520)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> DaVinci: 128 gpio irqs
> Generic PHY: Registered new driver
> SCSI subsystem initialized
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 4096 (order: 2, 16384 bytes)
> TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
> TCP: Hash tables configured (established 4096 bind 2048)
> TCP reno registered
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> squashfs: version 3.1 (2006/08/19) Phillip Lougher
> NTFS driver 2.1.27 [Flags: R/W].
> JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
> yaffs Nov 12 2008 11:35:58 Installing.
> JFS: nTxBlock = 981, nTxLock = 7853
> SGI XFS with no debug enabled
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> LTT : ltt-facilities init
> LTT : ltt-facility-core init in kernel
> LTT : ltt-relay init
> DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec
> Serial: 8250/16550 driver $Revision: 1.90 $ 3 ports, IRQ sharing disabled
> serial8250.0: ttyS0 at MMIO map 0x1c42000 mem 0xfec42000 (irq = 25) is a
> 16550A
> serial8250.0: ttyS1 at MMIO map 0x1c20400 mem 0xfed0c000 (irq = 53) is a
> 16550A
> serial8250.0: ttyS2 at MMIO map 0x1d0d000 mem 0xfed0d000 (irq = 61) is a
> 16550A
> RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
> netconsole: not configured, aborting
> Davinci EMAC MII Bus: probed
> MAC address is 00:0e:99:02:f0:30
> TI DaVinci EMAC Linux version updated 4.0
> i2c /dev entries driver
> physmap platform flash device: 01000000 at 60000000
> CFI: Found no physmap-flash.0 device at location zero
> physmap-flash physmap-flash.0: map_probe failed
> nand_davinci nand_davinci.0: Using 4-bit hardware ECC
> No NAND device found!!!
> nand_davinci nand_davinci.0: no nand device detected
> Creating 3 MTD partitions on "Windbond spi nand flash":
> 0x00000000-0x00020000 : "U-Boot"
> 0x00020000-0x00024000 : "U-Boot Environment"
> 0x00024000-0x00400000 : "Linux"
> dm_spi.0: davinci SPI Controller driver at 0xfec41000 (irq = 20) use_dma=1
> dm_spi.1: davinci SPI Controller driver at 0xfee12000 (irq = 56) use_dma=1
> ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
> ohci ohci.0: DA8xx OHCI
> ohci ohci.0: new USB bus registered, assigned bus number 1
> ohci ohci.0: irq 59, io mem 0x01e25000
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
> Initializing USB Mass Storage driver...
> usbcore: registered new driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new driver libusual
> musb_hdrc: version 6.0, cppi4.1-dma, host, debug=0
> Waiting for PHY clock good...
> musb_hdrc: ConfigData=0x06 (UTMI-8, dyn FIFOs, SoftConn)
> musb_hdrc: MHDRC RTL version 1.800
> musb_hdrc: setup fifo_mode 2
> musb_hdrc: 8/9 max ep, 3392/4096 memory
> musb_hdrc: hw_ep 0shared, max 64
> musb_hdrc: hw_ep 1tx, max 512
> musb_hdrc: hw_ep 1rx, max 512
> musb_hdrc: hw_ep 2tx, max 512
> musb_hdrc: hw_ep 2rx, max 512
> musb_hdrc: hw_ep 3tx, max 512
> musb_hdrc: hw_ep 3rx, max 512
> musb_hdrc: hw_ep 4shared, max 256
> musb_hdrc: USB Host mode controller at c8900000 using DMA, IRQ 58
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 1 port detected
> mice: PS/2 mouse device common for all mice
> rtc-da8xx rtc-da8xx.0: rtc intf: proc
> rtc-da8xx rtc-da8xx.0: rtc intf: dev (254:0)
> rtc-da8xx rtc-da8xx.0: rtc core: registered rtc-da8xx as rtc0
> rtc-da8xx rtc-da8xx.0: TI DA8xx Real Time Clock driver.
> IPv4 over IPv4 tunneling driver
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> rtc-da8xx rtc-da8xx.0: setting the system clock to 2000-01-05 00:00:46
> (94703044
> 6)
> Time: timer0_1 clocksource has been installed.
> Clock event device timer0_0 configured with caps set: 08
> Switched to high resolution mode on CPU 0
> usb 2-1: new high speed USB device using musb_hdrc and address 2
> usb 2-1: configuration #1 chosen from 1 choice
> scsi0 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 2
> usb-storage: waiting for device to settle before scanning
> Sending DHCP and RARP requests .., OK
> IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.24.241.69
> IP-Config: Complete:
> device=eth0, addr=10.24.241.69, mask=255.255.255.0, gw=10.24.241.1,
> host=10.24.241.69, domain=india.ext.ti.com, nis-domain=(none),
> bootserver=0.0.0.0, rootserver=10.24.241.126, rootpath=
> Looking up port of RPC 100003/2 on 10.24.241.126
> Looking up port of RPC 100005/1 on 10.24.241.126
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 152K
> Vendor: Generic Model: STORAGE DEVICE Rev: 9339
> Type: Direct-Access ANSI SCSI revision: 00
> SCSI device sda: 494080 512-byte hdwr sectors (253 MB)
> sda: Write Protect is off
> sda: Mode Sense: 03 00 00 00
> sda: assuming drive cache: write through
> SCSI device sda: 494080 512-byte hdwr sectors (253 MB)
> sda: Write Protect is off
> sda: Mode Sense: 03 00 00 00
> sda: assuming drive cache: write through
> sda: sda1
> sd 0:0:0:0: Attached scsi removable disk sda
> sd 0:0:0:0: Attached scsi generic sg0 type 0
> usb-storage: device scan complete
> ltt-control init
> LTT : ltt-facility-fs init in kernel
> LTT : ltt-facility-fs_data init in kernel
> LTT : ltt-facility-ipc init in kernel
> LTT : ltt-facility-kernel init in kernel
> LTT : ltt-facility-kernel_arch init in kernel
> LTT : ltt-facility-memory init in kernel
> LTT : ltt-facility-network init in kernel
> LTT : ltt-facility-network_ip_interface init in kernel
> LTT : ltt-facility-process init in kernel
> LTT : ltt-facility-socket init in kernel
> LTT : ltt-facility-statedump init in kernel
> LTT : ltt-facility-timer init in kernel
> 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 core
> Dumping facility timer
> Dumping facility socket
> Dumping facility memory
> Dumping facility fs
> Dumping facility fs_data
> Dumping facility network
> Dumping facility ipc
> Dumping facility kernel_arch
> Dumping facility kernel
> Dumping facility statedump
> Dumping facility process
> Dumping facility network_ip_interface
> ltt_statedump_start
> do_ltt_statedump
> trace_statedump_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
> root at 10.24.241.69:/home/saumya/lsp2.2/02/testing/lttng#
>
> How do I use LTTV in gui mode from host now? when I run lttv-gui, I get a
> GUI.
> Then I clicked on "insert tracing control module", gave root password and
> clicked on start:
>
Just :
scp -r /tmp/trace to your host
run
lttv-gui /path_to_trace
That's it.
The gui trace control part won't work. It only works if the target and
the host are the same machine.
Also double-check that the LTTV version you have is compatible with your
target kernel.
Mathieu
> I got following errors:
>
> An error occured in the su command : Unknown e rror 126
> bash: syntax error near unexpected token `lttv.real:10882'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
>
> (lttv.real:16361): GLib-GObject-WARNING **: g_object_set_valist: object
> class
> `G tkButton' has no property named `image'
> Executing (as root) : exec /usr/local/bin/lttctl -l /mnt/debugfs/ltt -t
> /tmp/trace1 -n trace -m flight -d -N 1
> Linux Trace Toolkit Trace Control 0.30-09112006
>
> Controlling trace : trace
>
> Create Trace Error: Failed to send netlink message: Connection refused
> wipro123
>
> ** (lttv.real:16361): WARNING **: An error occured in the su command :
> Operation not permitted
> What am I doing wrong here? I am not sure how to use LTTV from host.
> Also if I am doing some IO to MMC card through USB interface on my board,
> and I have started the trace then where will the trace data be captured?
>
> --Saumya
>
> On 11/12/08, saumya agarwal <cmks2002 at gmail.com> wrote:
> > Thanks a lot. I shall give it a try now.
> >
> > --Saumya
> >
> > On 11/12/08, Pierre-Marc Fournier <pierre-marc.fournier at polymtl.ca> wrote:
> > > saumya agarwal wrote:
> > > > Following exes are present in /usr/bin
> > > > ltrace
> > > > ltt-unload
> > > > lttd
> > > > lttv-gui
> > > > ltt-load
> > > > lttctl
> > > > lttv
> > > > lttv.real
> > > >
> > > > Does that means I don't have to install LTTng patches, or get LLT
> > > > control tools on target?
> > > > Only thing I need is to install LTTV on host?
> > >
> > > Exactly.
> > >
> > > >
> > > > --Saumya
> > > >
> > > > On 11/12/08, Mathieu Desnoyers <compudj at krystal.dyndns.org> wrote:
> > > >> If you already have a kernel with the LTTng patches applied, it
> probably
> > > >> comes from your distro. You should have a look at your
> distro-specific
> > > >> documentation to see if they provide some info about the specific
> LTTng
> > > >> version they use. But yes, all the pointers Pierre-Marc told you
> about
> > > >> should help you getting started.
> > > >>
> > > >> Mathieu
> > > >>
> > > >> * saumya agarwal (cmks2002 at gmail.com) wrote:
> > > >>> Thanks Marc, this info should get me started.
> > > >>>
> > > >>> My host linux machine has a different kernel version (2.6.9), so do
> I
> > > >>> need LTTV compatible with host or target?
> > > >>> In DA8xx kernel sources, I see a folder named LTT which has some
> > > >>> source files like ltt-control.c, ltt-core.c etc, so does that mean
> > > >>> that LTT control tools are already available in the kernel?
> > > >>>
> > > >>> --Saumya
> > > >>>
> > > >>>
> > > >>> On 11/12/08, Pierre-Marc Fournier <pierre-marc.fournier at polymtl.ca>
> wrote:
> > > >>>> Hello Saumya,
> > > >>>>
> > > >>>> saumya agarwal wrote:
> > > >>>>> I am using a DA8xx Primus EVM and I want to use LTTng to trace the
> > > >>>>> system. The kernel supports LTTng.
> > > >>>>> This is the first time I'll am working on it.
> > > >>>>>
> > > >>>>> I downloaded TraceToolkit-0.9.5 and untared it.
> > > >>>>> The patched I am getting are:
> > > >>>>> patch-ltt-linux-2.4.16-rthal5f-020415-1.14
> > > >>>>> patch-ltt-linux-2.4.16-s390-020422-1.14
> > > >>>>> patch-ltt-linux-2.4.16-vanilla-020415-1.14
> > > >>>>> patch-ltt-linux-2.5.7-vanilla-020415-1.14
> > > >>>>> patch-ltt-rtai-24.1.8-020317-1.14
> > > >>>>>
> > > >>>> Hmm, I don't know where you got this patch, but it is several years
> old.
> > > >>>> Please see the site http://ltt.polymtl.ca
> > > >>>> Have a look at the Compatibility list ("LTTng+LTTV versions
> > > >>>> compatibility" link) to see what you need for a 2.6.18 kernel. You
> > > >>>> probably need LTTng 0.6.41, ltt-control 0.30 and LTTV (the viewer)
> > > >>>> 0.8.72. You will also find the quickstart guide there which will
> help
> > > >>>> get you started.
> > > >>>>
> > > >>>> Note that since 2.6.18 is an old kernel. A lot of things changed
> since
> > > >>>> that time and the quickstart guide that is on the site now will not
> be
> > > >>>> in sync with this old version. I would recommend fetching the old
> guide
> > > >>>> from the svn repository.
> > > >>>>
> > > >>>>> But the linux kernel version for DA8xx is 2.6.18.
> > > >>>>> So can I use any of these patches?
> > > >>>> No, you need a much newer version of LTTng that was designed for
> 2.6.18.
> > > >>>>
> > > >>>>> One more doubt I had was, that we use this tool from host or on
> > > >>>>> target? Do I need a linux host machine, apply patches to its
> kernel,
> > > >>>>> and reboot it and then start using it OR I need to apply patches
> to my
> > > >>>>> DA8xx kernel and then start tracing on target itself?
> > > >>>> You install the patches on the target kernel. You also need the
> > > >>>> ltt-control tools on the target to control the tracing. You need to
> have
> > > >>>> enough disk space on the target to record the trace. Work on
> streaming
> > > >>>> is under way. Once you have the trace, you transfer it to the host
> and
> > > >>>> inspect it with LTTV.
> > > >>>>
> > > >>>>> I am kind of confused about its usage.
> > > >>>>> Could any one help me out with the exact procedure for using LTTng
> and
> > > >>>>> patches version (website) from where I can get required packages?
> > > >>>> Look at ltt.polymtl.ca and the quickstart guide.
> > > >>>>
> > > >>>> pmf
> > > >>>>
> > > >>> _______________________________________________
> > > >>> ltt-dev mailing list
> > > >>> ltt-dev at lists.casi.polymtl.ca
> > > >>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> > > >>>
> > > >> --
> > > >> Mathieu Desnoyers
> > > >> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE
> 3BAE 9A68
> > > >>
> > >
> > >
> >
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
More information about the lttng-dev
mailing list