<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>There are a few things to double-check:<br></div><div><br></div><div>- that the module holding the statedump event does not taint the kernel (is it signed ?)<br></div><div>- that there is no conflict between the lttng-modules from Ubuntu and the one you are using,<br></div><div><br></div><div>Also, I fixed TRACE_EVENT_MAP type of event declaration recently, but I don't think<br></div><div>it is related to your issue. This is only for the cases where the event name differs between the<br></div><div>Linux kernel tracepoint and the LTTng name.<br></div><div><br></div><div>Thanks,<br></div><div><br></div><div>Mathieu<br></div><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Krishanth TJ" <krishanthtj@gmail.com><br><b>To: </b>"Alexandre Montplaisir" <alexmonthy@voxpopuli.im><br><b>Cc: </b>lttng-dev@lists.lttng.org<br><b>Sent: </b>Monday, January 27, 2014 1:00:44 AM<br><b>Subject: </b>Re: [lttng-dev] Lttng state dump traces not present in 13.04 Ubuntu server distribution<br><div><br></div><div dir="ltr"><br><div class="gmail_extra">Yes, they do appear in "lttng list -k" event list.<br><div><br></div></div><div class="gmail_extra">Regards,<br></div><div class="gmail_extra">Krish.<br></div><div class="gmail_extra">
<br><div class="gmail_quote">On Fri, Jan 24, 2014 at 11:47 PM, Alexandre Montplaisir <span dir="ltr"><<a href="mailto:alexmonthy@voxpopuli.im" target="_blank">alexmonthy@voxpopuli.im</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hmm, ok, if you use "lttng list -k" do they appear in the list of<br>
available events?<br>
<br>
One other thing I can think about is that the statedump itself takes a<br>
little bit of time to execute, so the statedump events are never at the<br>
very start of the trace. So if your traces are very short it's possible<br>
to miss them entirely.<br>
<br>
Cheers,<br>
Alexandre<br>
<div class=""><div class="h5"><br>
<br>
On 14-01-24 08:54 AM, Krishanth TJ wrote:<br>
> Hi,<br>
><br>
> I have confirmed that the "lttng-modules-dkms" package was successfully<br>
> installed.<br>
><br>
> $ cat /usr/src/lttng-modules-2.3.x+stable/ChangeLog | head -4<br>
> 2013-09-28 LTTng modules 2.3.2<br>
> * Blacklist kernels 3.10.13 and 3.11.2<br>
><br>
> I have even confirmed with few debug printk's in lttng_statedump.ko that<br>
> the module is indeed loaded and the tracepoints are getting called. But<br>
> still babeltrace output fails to show lttng_statedump_events.<br>
><br>
> Am I missing something here?<br>
><br>
> Regards,<br>
> Krish.<br>
><br>
<br>
</div></div></blockquote></div><br></div></div>
<br>_______________________________________________<br>lttng-dev mailing list<br>lttng-dev@lists.lttng.org<br>http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev<br></blockquote><div><br><br></div><div><br></div><div>-- <br></div><div><span name="x"></span>Mathieu Desnoyers<br>EfficiOS Inc.<br>http://www.efficios.com<span name="x"></span><br></div></div></body></html>