Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: xufeng.zhang@windriver.com (xufeng zhang)
Subject: [ltt-dev] "Kernel/LTTV event size differs for event udpv4_rcv_extended: kernel 32, LTTV 28" error when view trace
Date: Mon, 08 Nov 2010 09:58:10 +0800	[thread overview]
Message-ID: <4CD75932.7080609@windriver.com> (raw)
In-Reply-To: <4CD75636.1020305@polymtl.ca>

On 11/08/2010 09:45 AM, Benjamin Poirier wrote:
> On 05/11/10 02:24 AM, xufeng zhang wrote:
>    
>> Hi,
>> I'm using ltt-control-0.86 and lttv-0.12.31 on ARM to trace the kernel,
>> however,
>>      
> Hello,
>
> Which version of the kernel tracer patches are you using?
>    
We are using linux-kernel-2.6.34, but I can't figure out which version 
of LTTpng we are using.

Thanks,
Xufeng Zhang
> -Ben
>
>    
>> I cannot view the trace after I have successfully generated, here is the
>> error
>> when I run 'lttv-gui -t trace1' command:
>> ** Message: statistics viewer : background computation data ready.
>>
>> ** (lttv.real:6559): WARNING **: Cannot find pin_in in schedchange 671
>>
>> ** ERROR **: Kernel/LTTV event size differs for event
>> udpv4_rcv_extended: kernel 32, LTTV 28
>> aborting...
>> /usr/local/bin/lttv-gui: line 10:  6559 Aborted
>> $LTTV_CMD.real -m lttvwindow -m guievents -m guifilter -m guicontrolflow
>> -m resourceview -m guistat
>>
>>
>> And I found another people met the same problem on MIPS32, a patch have
>> also been provided for MIPS32.
>> Here is the similar code in ARM trace-clock.c:
>> linux/arch/arm/mach-omap2/trace-clock.c line 537
>> void get_trace_clock(void)
>> {
>>          spin_lock(&trace_clock_lock);
>>          if (trace_clock_refcount++)
>>                  goto end;
>>          _start_trace_clock();
>> end:
>>          spin_unlock(&trace_clock_lock);
>> }
>> EXPORT_SYMBOL_GPL(get_trace_clock);
>>
>> void put_trace_clock(void)
>> {
>>          spin_lock(&trace_clock_lock);
>>          WARN_ON(trace_clock_refcount<= 0);
>>          if (trace_clock_refcount != 1)
>>                  goto end;
>>          _stop_trace_clock();
>> end:
>>          trace_clock_refcount--;
>>          spin_unlock(&trace_clock_lock);
>> }
>> EXPORT_SYMBOL_GPL(put_trace_clock);
>>
>> Could anybody figure out what's wrong with the kernel code? Any
>> suggestion would be appreciated.
>>
>>
>> Thanks,
>> Xufeng Zhang
>>
>>
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>>      
>    




  reply	other threads:[~2010-11-08  1:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05  6:24 xufeng zhang
2010-11-08  1:45 ` Benjamin Poirier
2010-11-08  1:58   ` xufeng zhang [this message]
2010-11-08  5:20   ` xufeng zhang
2010-11-08  9:55     ` Mathieu Desnoyers
2010-11-09  7:29       ` xufeng zhang
2010-11-09 11:45         ` Mathieu Desnoyers
2010-11-09 11:57           ` Mathieu Desnoyers
2010-11-10  7:14             ` xufeng zhang
2010-11-10  7:19             ` xufeng zhang
2010-11-10 14:08               ` Mathieu Desnoyers
2010-11-10 15:14                 ` Mathieu Desnoyers
     [not found]     ` <AANLkTimgLAWUwF2jhH6R=2JUZW8C9PYGN1dzSzZ9Wws7@mail.gmail.com>
2010-11-09  7:03       ` xufeng zhang
2010-11-09  7:03         ` xufeng zhang
2010-11-09  7:03         ` xufeng zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CD75932.7080609@windriver.com \
    --to=xufeng.zhang@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox