[ltt-dev] lttv crashed in tracefile.c:1582
Mathieu Desnoyers
compudj at krystal.dyndns.org
Wed Mar 31 16:13:20 EDT 2010
* Dany Madden (dany4madden at gmail.com) wrote:
> On Wed, Mar 31, 2010 at 10:24 AM, Mathieu Desnoyers <
> compudj at krystal.dyndns.org> wrote:
>
> > * Dany Madden (dany4madden at gmail.com) wrote:
> > > Hello,
> > >
> > > Please take a look at this lttv error with the mainline kernel
> > > 2.6.32.9 on ppc64.
> > >
> > > lttng: patch-2.6.32.9-lttng-0.198
> > > lttv-0.12.30-02102010
> > > ltt-control-0.79-01022010
> > >
> > > LTTV crashed with this error:
> > >
> > > ERROR:tracefile.c:1582:ltt_update_event_size: assertion failed: (info !=
> > NULL)
> > > /usr/bin/lttv: line 15: 2696 Aborted $0.real $*
> > >
> > >
> > > CONFIG_LTT=y
> > > CONFIG_LTT_FILTER=m
> > > # CONFIG_HAVE_LTT_DUMP_TABLES is not set
> > > CONFIG_LTT_RELAY=y
> > > CONFIG_LTT_RELAY_LOCKLESS=y
> > > # CONFIG_LTT_RELAY_IRQOFF is not set
> > > # CONFIG_LTT_RELAY_LOCKED is not set
> > > CONFIG_LTT_SERIALIZE=y
> > > CONFIG_LTT_FAST_SERIALIZE=y
> > > CONFIG_LTT_TRACEPROBES=m
> > > CONFIG_LTT_TRACE_CONTROL=m
> > > CONFIG_LTT_TRACER=y
> > > # CONFIG_LTT_ALIGNMENT is not set
> > > CONFIG_LTT_CHECK_ARCH_EFFICIENT_UNALIGNED_ACCESS=y
> > > # CONFIG_LTT_DEBUG_EVENT_SIZE is not set
> > > CONFIG_LTT_USERSPACE_EVENT=m
> > > CONFIG_LTT_VMCORE=y
> > > CONFIG_LTT_STATEDUMP=m
> > > CONFIG_LTT_KPROBES=m
> > > # CONFIG_LTT_ASCII is not set
> > >
> > >
> > > > modprobe ltt-trace-control
> > > > modprobe ipc-trace
> > > > modprobe kernel-trace
> > > > modprobe mm-trace
> > > > modprobe fs-trace
> > > > modprobe syscall-trace
> > > > modprobe trap-trace
> > >
> > > > ltt-armall
> > > > lttctl -C -w /tmp/trace1 trace1
> > > > lttctl -D trace1
> > > > lttv -m textDump -t /tmp/trace1
> > > **
> > > ERROR:tracefile.c:1582:ltt_update_event_size: assertion failed: (info !=
> > NULL)
> > > /usr/bin/lttv: line 15: 2696 Aborted $0.real $*
> > >
> > > This post,
> > http://lists.casi.polymtl.ca/pipermail/ltt-dev/2010-February/002189.html,
> > > describes the same error on 32 bit system. By not having the
> > > LTT_ALIGNMENT set, shouldn't it just work in my case?
> > >
> > > Thanks in advance for your help!
> >
> > A few questions:
> >
> > - the trace is taken on a ppc64 machine. Is is viewed on a ppc64 too, or
> > on a different arch size/endianness ?
> >
>
> Trace collected and viewed on the same ppc64 system.
>
>
> >
> > - Can you provide some information about the content of the trace
> > directory ? (files, file size)
> >
>
> The files in the trace directory are all the same size??
>
> > /tmp/trace3 # ls -l
> total 2448
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 fs_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 fs_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 fs_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 fs_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 input_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 input_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 input_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 input_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 ipc_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 ipc_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 ipc_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 ipc_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 kernel_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 kernel_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 kernel_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 kernel_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 metadata_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 metadata_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 metadata_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 metadata_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 mm_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 mm_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 mm_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 mm_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 module_state_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 module_state_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 module_state_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 module_state_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 softirq_state_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 softirq_state_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 softirq_state_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 softirq_state_3
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 swap_state_0
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 swap_state_1
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 swap_state_2
> -rwxr-xr-x 1 root root 65536 2010-03-31 19:32 swap_state_3
>
Oh, that's a pretty good hint. Although I tried to make everything as
generic as possible, I think LTTV assumes that the page size is 4k.
However, recent ppc64 kernels have a 64k page size. So I'm fairly sure
that this is where the problem comes from.
Can you send me (privately) a tarball of your trace so I can see what I
can do with LTTV to support it ?
Thanks,
Mathieu
>
> >
> > Also, trying to enable "CONFIG_LTT_DEBUG_EVENT_SIZE" might help by
> > providing extra self-check on trace metadata consistency.
> >
> > Rebuilt the kernel with CONFIG_LTT_DEBUG_EVENT_SIZE=y , recollected the
> trace and viewed it. I still see the same error and did notice anything else
> different than it was before.
>
>
> > Thanks,
> >
> > Mathieu
> >
> > >
> > > Dany Madden
> >
> > > _______________________________________________
> > > ltt-dev mailing list
> > > ltt-dev at lists.casi.polymtl.ca
> > > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> >
> >
> > --
> > Mathieu Desnoyers
> > Operating System Efficiency R&D Consultant
> > EfficiOS Inc.
> > http://www.efficios.com
> >
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
More information about the lttng-dev
mailing list