From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] lttctl stop command hangs on ARM926 processor
Date: Thu, 23 Jun 2011 11:34:46 -0400 [thread overview]
Message-ID: <BLU0-SMTP46E6536E384E2E1AF295B496530@phx.gbl> (raw)
In-Reply-To: <BANLkTintS8v9=2NMB=EtJP480nMjsL3k5Q@mail.gmail.com>
There is always the option to backport the lttng patches from 2.6.31.6
to 2.6.30.
The compatibility list is more a guide than a strict list of
"incompatibility", so you might be lucky and get a non-compabile lttng
to apply mostly fine on an older kernel. Your mileage may vary.
Mathieu
* Francis Leblanc (fleblanclists at gmail.com) wrote:
> Ok, do I absolutely need to update the kernel in order to apply the
> patchset 0.170 ?
> lttng 0.170 seems to correspond to kernel 2.6.31.6 ...
>
> We are using a SDK from a 3rd party and upgrading the kernel would
> require more tests on our end.
>
> Francis
>
> On Thu, Jun 23, 2011 at 10:58 AM, Mathieu Desnoyers
> <compudj at krystal.dyndns.org> wrote:
> > * Francis Leblanc (fleblanclists at gmail.com) wrote:
> >> Hi everyone,
> >>
> >> I am trying to get LTTng kernel tracer work on an ARM target.
> >> I can start the kernel tracing with lttctl -C -w /tmp/trace1 trace1,
> >> but when I stop it with lttctl -D trace1, it hangs.
> >> (see console.log and .config attachments)
> >>
> >> Setup information :
> >> kernel 2.6.30
> >> LTTng 0.159 (patch-2.6.30-lttng-0.159)
> >> ltt-control-0.75-15112009
> >
> > If you look at the compatibility list:
> >
> > http://git.lttng.org/?p=lttv.git;a=blob_plain;f=doc/developer/lttng-lttv-compatibility.html;hb=HEAD
> >
> > a few fixes came into LTTng around versions 0.166 and 0.170 to deal with
> > trace teardown problems. I would therefore recommend you first try
> > upgrading your lttng version.
> >
> > Thanks for the detailed report,
> >
> > Mathieu
> >
> >>
> >> Thanks in advance !
> >>
> >> Francis Leblanc
> >
> >
> >
> >> _______________________________________________
> >> 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
prev parent reply other threads:[~2011-06-23 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 14:17 Francis Leblanc
2011-06-23 14:17 ` Francis Leblanc
2011-06-23 14:17 ` Francis Leblanc
2011-06-23 14:58 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP52D8615453BBAFC92B63E696530@phx.gbl>
2011-06-23 15:09 ` Francis Leblanc
2011-06-23 15:34 ` Mathieu Desnoyers [this message]
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=BLU0-SMTP46E6536E384E2E1AF295B496530@phx.gbl \
--to=compudj@krystal.dyndns.org \
/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