[lttng-dev] call trace while using lttng in petalinux 2019.2 (kernel 4.19)
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 10c0 [ 163.995379] Mem abort info: [ 163.998179] ESR = 0x9605 [ 164.001233] Exception class = DABT (current EL), IL = 32 bits [ 164.007149] SET = 0, FnV = 0 [ 164.010203] EA = 0, S1PTW = 0 [ 164.01] Data abort info: [ 164.016218] ISV = 0, ISS = 0x0005 [ 164.020054] CM = 0, WnR = 0 [ 164.023028] user pgtable: 4k pages, 39-bit VAs, pgdp = df6dd54e [ 164.029646] [10c0] pgd=, pud= [ 164.036447] Internal error: Oops: 9605 [#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: 6005 (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 : ff8011613a40 [ 164.091314] x29: ff8011613a40 x28: ff801163f000 [ 164.096618] x27: 0100 x26: ff800813c958 [ 164.101921] x25: ff8000e22758 x24: [ 164.107225] x23: 10c0 x22: ff8000e42ed8 [ 164.112528] x21: ffc87accc400 x20: ff8000e42ef8 [ 164.117832] x19: 0001 x18: [ 164.123135] x17: x16: [ 164.128439] x15: x14: [ 164.133742] x13: x12: [ 164.139046] x11: 0001 x10: 0101010101010101 [ 164.144349] x9 : 6d64686b625e6f38 x8 : 706d75645f6c6f63 [ 164.149653] x7 : 6f746f72705f7039 x6 : ffc8778d5ec1 [ 164.154957] x5 : ff8009458000 x4 : [ 164.160260] x3 : ff8000db77a0 x2 : ffc87828a380 [ 164.165563] x1 : 0007 x0 : ff8000d13048 [ 164.170869] Process modprobe (pid: 4955, stack limit = 0xe6162018) [ 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) 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
Re: [lttng-dev] call trace while using lttng in petalinux 2019.2 (kernel 4.19)
- 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 > 10c0 > [ 163.995379] Mem abort info: > [ 163.998179] ESR = 0x9605 > [ 164.001233] Exception class = DABT (current EL), IL = 32 bits > [ 164.007149] SET = 0, FnV = 0 > [ 164.010203] EA = 0, S1PTW = 0 > [ 164.01] Data abort info: > [ 164.016218] ISV = 0, ISS = 0x0005 > [ 164.020054] CM = 0, WnR = 0 > [ 164.023028] user pgtable: 4k pages, 39-bit VAs, pgdp = df6dd54e > [ 164.029646] [10c0] pgd=, pud= > [ 164.036447] Internal error: Oops: 9605 [#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: 6005 (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 : ff8011613a40 > [ 164.091314] x29: ff8011613a40 x28: ff801163f000 > [ 164.096618] x27: 0100 x26: ff800813c958 > [ 164.101921] x25: ff8000e22758 x24: > [ 164.107225] x23: 10c0 x22: ff8000e42ed8 > [ 164.112528] x21: ffc87accc400 x20: ff8000e42ef8 > [ 164.117832] x19: 0001 x18: > [ 164.123135] x17: x16: > [ 164.128439] x15: x14: > [ 164.133742] x13: x12: > [ 164.139046] x11: 0001 x10: 0101010101010101 > [ 164.144349] x9 : 6d64686b625e6f38 x8 : 706d75645f6c6f63 > [ 164.149653] x7 : 6f746f72705f7039 x6 : ffc8778d5ec1 > [ 164.154957] x5 : ff8009458000 x4 : > [ 164.160260] x3 : ff8000db77a0 x2 : ffc87828a380 > [ 164.165563] x1 : 0007 x0 : ff8000d13048 > [ 164.170869] Process modprobe (pid: 4955, stack limit = 0xe6162018) > [ 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)
Re: [lttng-dev] Add support for the LOONGARCH architecture
Hi,
I'm just checking if you have received my message ? I want to understand what is
going on here before merging your contribution into liburcu.
Thanks,
Mathieu
- On Jan 25, 2022, at 4:36 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> Hi,
>
> I notice that the loongarch enablement patch defines:
>
> #define UATOMIC_HAS_ATOMIC_BYTE
> #define UATOMIC_HAS_ATOMIC_SHORT
>
> I tried looking into
>
>
> https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1-EN.html#atomic-memory-access-instructions
>
> to figure out which atomic instructions or LL/SC would be used to target 1
> and 2
> byte
> variables atomically, but could only find instructions for word and
> double-word:
>
> 2.2.7.1. AM{SWAP/ADD/AND/OR/XOR/MAX/MIN}[DB].{W/D}, AM{MAX/MIN}[_DB].{WU/DU}
> 2.2.7.2. LL.{W/D}, SC.{W/D}
>
> What am I missing here ?
>
> Thanks,
>
> Mathieu
>
> - On Jan 24, 2022, at 6:59 AM, lttng-dev lttng-dev@lists.lttng.org wrote:
>
>> Unfortunately, the qemu approach does not help much in testing that the
>> liburcu implementation works correctly on a given architecture's
>> specific memory model.
>>
>> liburcu relies heavily on memory ordering, and liburcu-cds relies on
>> both memory ordering and atomic operations and the memory ordering
>> guarantees associated with them.
>>
>> So if there is any way we could get our hands on real hardware, it
>> would be very much relevant for liburcu testing.
>>
>> Thanks,
>>
>> Mathieu
>>
>> - On Jan 24, 2022, at 3:02 AM, 张文龙 zhangwenl...@loongson.cn wrote:
>>
>>> I'm glad the new architecture can be accepted，At present, our machines are
>>> in
>>> short supply.I need to go through a very complicated process to provide
>>> machines, Can qemu emulator work?
>>>
>>>
>>> > -原始邮件-
>>> > 发件人: "Mathieu Desnoyers"
>>> > 发送时间: 2022-01-20 23:59:52 (星期四)
>>> > 收件人: "张文龙"
>>> > 抄送: lttng-dev
>>> > 主题: Re: [lttng-dev] Add support for the LOONGARCH architecture
>>> >
>>> > - On Jan 19, 2022, at 11:03 PM, lttng-dev lttng-dev@lists.lttng.org
>>> wrote:
>>> >
>>> > > Hello, I'm excited to contribute to userspace-rcu, I added
>>> loongarch
>>> > > architecture for userspace-rcu（ The patch file is
>>> > > 0001-Add-support-for-the-LOONGARCH-architecture.patch )
>>> >
>>> > > I have compiled and verified locally (the build log is
>>> build_log.txt
>>> ),and then
>>> > > i runed make check（ the make check log is make_check_log.txt ），
>>> make
>>> > > regtest（the make regtest log is make_regtest_log.txt ） ， make
>>> short_bench (the
>>> > > make short_bench log is make_short_bench_log.txt ),make
>>> long_bench(the
>>> make
>>> > > long_bench log is make_long_bench_log.txt )
>>> >
>>> > This is great, thanks !
>>> >
>>> > By the way, is there any way EfficiOS could add two loongarch test
>>> boards
>>> into
>>> > our test rack for automated CI testing ? See https://ci.lttng.org
>>> >
>>> > We typically deploy at least two boards for each given architecture for
>>> redundancy
>>> > and availability for both CI and development use.
>>> >
>>> > This would help ensuring we catch liburcu regressions in the loongarch
>>> architecture
>>> > in the future.
>>> >
>>> > Thanks,
>>> >
>>> > Mathieu
>>> >
>>> >
>>> > > 本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部
>>> > > 分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。
>>> > > This email and its attachments contain confidential information
>>> from
>>> Loongson
>>> > > Technology , which is intended only for the person or entity whose
>>> address is
>>> > > listed above. Any use of the information contained herein in any
>>> way
>>> > > (including, but not limited to, total or partial disclosure,
>>> reproduction or
>>> > > dissemination) by persons other than the intended recipient(s) is
>>> prohibited.
>>> > > If you receive this email in error, please notify the sender by
>>> phone
>>> or email
>>> > > immediately and delete it.
>>> > > ___
>>> > > 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
>>>
>>>
>>> 本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。
>>> This email and its attachments contain confidential information from
>>> Loongson
>>> Technology , which is intended only for the person or entity whose address
>>> is
>>> listed above. Any use of the information contained herein in any way
>>> (including, but not limited to, total or partial disclosure, reproduction or
>>> dissemination) by persons other than the intended recipient(s) is
>>> prohibited.
>>> If you receive this email in error, please notify the sender by phone or
>>> email
>>> immediately and delete it.
>>
>> --
>> Mathieu Desnoyers
>> EfficiOS Inc.
>> http://www.efficios.com
>>
