All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: GOLLAMUDI MADHAN MOHAN <madhan.mohan@5g.iith.ac.in>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] call trace while using lttng in petalinux 2019.2 (kernel 4.19)
Date: Tue, 15 Mar 2022 11:49:42 -0400 (EDT)	[thread overview]
Message-ID: <795806806.151478.1647359382157.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAB9=ZW6FEj+zXnVcSaCGCSWF54cZDEv5_25-F0D1SEZHZaZ=rw@mail.gmail.com>



----- On Mar 15, 2022, at 2:48 AM, lttng-dev lttng-dev@lists.lttng.org wrote:

> Dear Sir/Madam,
> I am Madhan , working as an embedded engineer in 5GTB. I am using lttng in
> petalinux 2019.2(kernel 4.19) .And getting a call Trace error. Refer the below
> log for more details.

> root@xilinx-zcu111-2019_2:~# lttng create
> Spawning a session daemon
> [ 163.902282] lttng_kretprobes: loading out-of-tree module taints kernel.
> [ 163.987461] Unable to handle kernel paging request at virtual address
> 00000000000010c0
> [ 163.995379] Mem abort info:
> [ 163.998179] ESR = 0x96000005
> [ 164.001233] Exception class = DABT (current EL), IL = 32 bits
> [ 164.007149] SET = 0, FnV = 0
> [ 164.010203] EA = 0, S1PTW = 0
> [ 164.013333] Data abort info:
> [ 164.016218] ISV = 0, ISS = 0x00000005
> [ 164.020054] CM = 0, WnR = 0
> [ 164.023028] user pgtable: 4k pages, 39-bit VAs, pgdp = 00000000df6dd54e
> [ 164.029646] [00000000000010c0] pgd=0000000000000000, pud=0000000000000000
> [ 164.036447] Internal error: Oops: 96000005 [#1] SMP
> [ 164.041318] Modules linked in: lttng_tracer(O+) lttng_statedump(O)
> lttng_ftrace(O) lttng_kprobes(O) lttng_clock(O) lttng_lib_ring_buffer(O)
> lttng_kretprobes(O) uio_pdrv_genirq
> [ 164.056963] CPU: 1 PID: 4955 Comm: modprobe Tainted: G O 4.19.0-xilinx-v2019.2
> #1
> [ 164.065734] Hardware name: ZynqMP ZCU111 RevA (DT)
> [ 164.070510] pstate: 60000005 (nZCv daif -PAN -UAO)
> [ 164.075429] pc : lttng_tracepoint_notify+0x188/0x228 [lttng_tracer]
> [ 164.081767] lr : lttng_tracepoint_notify+0x14c/0x228 [lttng_tracer]
> [ 164.088016] sp : ffffff8011613a40
> [ 164.091314] x29: ffffff8011613a40 x28: ffffff801163f000
> [ 164.096618] x27: 0000000000000100 x26: ffffff800813c958
> [ 164.101921] x25: ffffff8000e22758 x24: 0000000000000000
> [ 164.107225] x23: 00000000000010c0 x22: ffffff8000e42ed8
> [ 164.112528] x21: ffffffc87accc400 x20: ffffff8000e42ef8
> [ 164.117832] x19: 0000000000000001 x18: 0000000000000000
> [ 164.123135] x17: 0000000000000000 x16: 0000000000000000
> [ 164.128439] x15: ffffffffffffffff x14: 0000000000000000
> [ 164.133742] x13: 0000000000000000 x12: 0000000000000000
> [ 164.139046] x11: 0000000000000001 x10: 0101010101010101
> [ 164.144349] x9 : 6d64686b625e6f38 x8 : 706d75645f6c6f63
> [ 164.149653] x7 : 6f746f72705f7039 x6 : ffffffc8778d5ec1
> [ 164.154957] x5 : ffffff8009458000 x4 : 0000000000000000
> [ 164.160260] x3 : ffffff8000db77a0 x2 : ffffffc87828a380
> [ 164.165563] x1 : 0000000000000007 x0 : ffffff8000d13048
> [ 164.170869] Process modprobe (pid: 4955, stack limit = 0x00000000e6162018)
> [ 164.177725] Call trace:
> [ 164.180235] lttng_tracepoint_notify+0x188/0x228 [lttng_tracer]
> [ 164.186148] register_tracepoint_module_notifier+0x6c/0x98
> [ 164.191709] lttng_tracepoint_init+0x54/0xc80 [lttng_tracer]
> [ 164.197438] lttng_events_init+0x4c/0x1e0 [lttng_tracer]
> [ 164.202734] do_one_initcall+0x68/0x1ec
> [ 164.206562] do_init_module+0x60/0x1f0
> [ 164.210302] load_module+0x1ca0/0x2270
> [ 164.214035] __se_sys_finit_module+0xc0/0xd0
> [ 164.218288] __arm64_sys_finit_module+0x24/0x30
> [ 164.222802] el0_svc_common+0x98/0x100
> [ 164.226543] el0_svc_handler+0x74/0x90
> [ 164.230275] el0_svc+0x8/0xc
> [ 164.233142] Code: 6b18003f 54fffc49 f9415c00 b8b8d817 (f94002f3)
> [ 164.239226] ---[ end trace c1cc2d1f9d55794a ]---
> [ 195.613567] lttng_ring_buffer_client_overwrite: gave up waiting for init of
> module lttng_tracer.
> [ 195.622371] lttng_ring_buffer_client_overwrite: Unknown symbol
> lttng_transport_unregister (err -16)
> ^C
> root@xilinx-zcu111-2019_2:~# uname -a
> Linux xilinx-zcu111-2019_2 4.19.0-xilinx-v2019.2 #1 SMP Mon Mar 14 15:09:26 UTC
> 2022 aarch64 GNU/Linux
> root@xilinx-zcu111-2019_2:~# uname -a
> Linux xilinx-zcu111-2019_2 4.19.0-xilinx-v2019.2 #1 SMP Mon Mar 14 15:09:26 UTC
> 2022 aarch64 GNU/Linux
> root@xilinx-zcu111-2019_2:~# [ 226.333565] lttng_ring_buffer_client_overwrite:
> gave up waiting for init of module lttng_tracer.
> [ 226.342368] lttng_ring_buffer_client_overwrite: Unknown symbol lttng_last_tsc
> (err -16)
> [ 257.053564] lttng_ring_buffer_client_overwrite: gave up waiting for init of
> module lttng_tracer.
> [ 257.062358] lttng_ring_buffer_client_overwrite: Unknown symbol
> lttng_transport_register (err -16)
> [ 287.773562] lttng_ring_buffer_client_overwrite: gave up waiting for init of
> module lttng_tracer.
> [ 287.782356] lttng_ring_buffer_client_overwrite: Unknown symbol
> lttng_transport_unregister (err -16)
> [ 318.493567] lttng_ring_buffer_client_overwrite: gave up waiting for init of
> module lttng_tracer.
> [ 318.502364] lttng_ring_buffer_client_overwrite: Unknown symbol lttng_last_tsc
> (err -16)
> [ 349.213564] lttng_ring_buffer_client_overwrite: gave up waiting for init of
> module lttng_tracer.
> [ 349.222363] lttng_ring_buffer_client_overwrite: Unknown symbol
> lttng_transport_register (err -16)

What is the installed lttng-modules version ? 

You can query it with modinfo /lib/modules/$(uname -r)/extra/lttng-tracer.ko

Thanks, 

Mathieu 

> Thank You
> with regards
> G Madhan Mohan

> Disclaimer:- This footer text is to convey that this email is sent by one of the
> users of IITH. So, do not mark it as SPAM.
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2022-03-15 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15  6:48 [lttng-dev] call trace while using lttng in petalinux 2019.2 (kernel 4.19) GOLLAMUDI MADHAN MOHAN via lttng-dev
2022-03-15 15:49 ` Mathieu Desnoyers via lttng-dev [this message]
     [not found]   ` <CAB9=ZW6nDGJ+xv+6h4FHL2-63J9YE5P1KoAyvB+yWAx0rr46wA@mail.gmail.com>
2022-03-16 13:25     ` Mathieu Desnoyers via lttng-dev
2022-03-16 14:54       ` Michael Jeanson via lttng-dev
2022-03-16 19:48         ` 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=795806806.151478.1647359382157.JavaMail.zimbra@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=madhan.mohan@5g.iith.ac.in \
    --cc=mathieu.desnoyers@efficios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.