From: Jonathan Rajotte-Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: Lukasz Domowy <lukasz.odw39@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] lttng_lib_ring_buffer: section 24 reloc 0 sym '': relocation 42 out of range
Date: Thu, 28 May 2020 09:31:32 -0400 [thread overview]
Message-ID: <20200528133132.GB6269@joraj-alpa> (raw)
Message-ID: <20200528133132.A8ATxOL0njDviUkyxdf9-aFRaSA58v_oxKkFXvzBgWA@z> (raw)
In-Reply-To: <CAGK+5gW_7Lo3O4oYW8jVJqDiUby6xoRyL3-JJQDQ8VYLG7WPAg@mail.gmail.com>
Hi Lukasz,
Is the problem reproducible on the qemu arm target (yocto) ?
On Thu, May 28, 2020 at 01:51:12PM +0200, Lukasz Domowy via lttng-dev wrote:
> Hello,
>
> First - of all: thank you very much for efforts to develop and
> maintain LTTng. It's very useful tool!
> I used it so far on PowerPC targets and now I try to run it on ARM:
> Cyclone5 ARMv7 CPU.
>
> When trying to run LTTng I get:
>
> # lttng list --kernel
> [ 2012.822578] lttng_lib_ring_buffer: section 24 reloc 0 sym '':
> relocation 42 out of range (0x7f05827c -> 0xc0cd7358)
> Error: Unable to list kernel events: Kernel tracer not available
> Error: Command error
>
> Do you have any hints how to fix it?
>
> I found https://bugs.lttng.org/issues/1173 but enabling
> CONFIG_ARM_MODULE_PLTS did not help.
>
> I use LTTng from Yocto 3.0.2 with custom kernel 4.14.134-rt63-rt:
>
> # lttng -V
> lttng (LTTng Trace Control) 2.10.7 - KeKriek
>
> All options recommended from documentation are enabled:
> root@cyclone5:~# zcat /proc/config.gz | grep -i modules
> CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
> CONFIG_MODULES_USE_ELF_REL=y
> CONFIG_MODULES=y
> CONFIG_MODULES_TREE_LOOKUP=y
> # Xtables combined modules
> # User Modules And Translation Layers
> root@cyclone5:~# zcat /proc/config.gz | grep -i kallsyms
> CONFIG_KALLSYMS=y
> # CONFIG_KALLSYMS_ABSOLUTE_PERCPU is not set
> CONFIG_KALLSYMS_BASE_RELATIVE=y
> root@cyclone5:~# zcat /proc/config.gz | grep -i high_res_timers
> CONFIG_HIGH_RES_TIMERS=y
> root@cyclone5:~# zcat /proc/config.gz | grep -i tracepoints
> CONFIG_TRACEPOINTS=y
> CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
>
> Thank you in advance!
>
> Best regards,
> Lukasz
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-05-28 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 11:51 lttng_lib_ring_buffer: section 24 reloc 0 sym '': relocation 42 out of range Lukasz Domowy via lttng-dev
2020-05-28 11:51 ` [lttng-dev] " Lukasz Domowy via lttng-dev
2020-05-28 13:31 ` Jonathan Rajotte-Julien via lttng-dev [this message]
2020-05-28 13:31 ` Jonathan Rajotte-Julien via lttng-dev
2020-05-28 13:31 ` Mathieu Desnoyers via lttng-dev
2020-05-28 13:31 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
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=20200528133132.GB6269@joraj-alpa \
--to=lttng-dev@lists.lttng.org \
--cc=jonathan.rajotte-julien@efficios.com \
--cc=lukasz.odw39@gmail.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;
as well as URLs for NNTP newsgroup(s).