From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 995D8A052A for ; Tue, 26 Jan 2021 22:55:33 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 73E63140D0E; Tue, 26 Jan 2021 22:55:33 +0100 (CET) Received: from mail-pg1-f181.google.com (mail-pg1-f181.google.com [209.85.215.181]) by mails.dpdk.org (Postfix) with ESMTP id 7641D140D0D for ; Tue, 26 Jan 2021 22:55:31 +0100 (CET) Received: by mail-pg1-f181.google.com with SMTP id c132so137092pga.3 for ; Tue, 26 Jan 2021 13:55:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XaKT7uyJab/5qtt6RWkcHvqQT62NXsdsBZS3yDij3jA=; b=KpKQBvZHggawlM80I8Y8xU/B/vB/LcJl3AYsuyKzwmC55Od7oldB+Te0o54LPvQmfZ HZbZDte5xydpHXX8TUj9IGIksENAqyt0sm4cjWq8L69XuoC8uYTLUMNSyONFWa2YoLw1 eae5khS/0FdwysZso4hvhVPt0A57p4GONz+5o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XaKT7uyJab/5qtt6RWkcHvqQT62NXsdsBZS3yDij3jA=; b=oBqF4o5A7oMcTWEdCxEwRe5qEuARE3euKsjLpdjcMTB+Y5a3xXgCTs8I2DPOUKu+G0 F4lwDBix8uXrF7iMkl8gr73vKsQYZe/zJMUPewMs45Cc8Ppo1DoYgrt8c4TqtfhesNn3 buUbt0yYN35ZCXHLtr68nqKhYGVzZ29IlvmJIKtCkJluoLKt0u1ROXQKGaLWPmMZjrD2 s209k+WALZOh/tT2MWA0m39ogi7CUwPQCbiNDk/bqecyU+5RYI4DhyIR2V0TWgUl3VE5 KhfWcEkyNaERBHw8deR9GVbCQ6otIdfstaDDau5ljRYhJChg49t1MYLc1d1bAThBBIXa UMrw== X-Gm-Message-State: AOAM533jxS8Kww1d0sMTG6SkO54wvieMq3/60sGdVff7Vhm6oauZ+B1b S+KWJS5RaxA7IQuOiO+i5jsePsmQH6D6J4VqXenQIQ== X-Google-Smtp-Source: ABdhPJyNUMz+6ycC7FA4Mlfd1W5bHs3+Fj0V9HCRvYxRRONi49VCMHc0/PGrI2n2+NhlibhJShQ5jnkPP0HEfLK3ZHs= X-Received: by 2002:a65:62cd:: with SMTP id m13mr5430928pgv.108.1611698130649; Tue, 26 Jan 2021 13:55:30 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Liu Date: Tue, 26 Jan 2021 16:54:54 -0500 Message-ID: To: Ajit Khaparde Cc: ci@dpdk.org, dpdklab Content-Type: multipart/alternative; boundary="000000000000901e5005b9d4b6dc" Subject: Re: [dpdk-ci] [DPDKLAB] 25G Broadcom NIC in Arm hardware X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" --000000000000901e5005b9d4b6dc Content-Type: text/plain; charset="UTF-8" Hi Ajit, Sorry for the late reply. You can ssh into the machine using the same VPN Username and Password. Can you try and see if that works? Informatio: arm-dell.dpdklab.iol.unh.edu - dts - located in /opt/dts - Trex - located in /opt/trex/v2.87 arm-gigabyte.dpdklab.iol.unh.edu - dpdk - located in /root/dpdk Thanks, David On Tue, Jan 19, 2021 at 5:20 PM Ajit Khaparde wrote: > Hi David, > Thanks for pinging me. Do you think I could login into the setup and > see what is happening? > I do have the credentials for two systems in your lab - > rhea.dpdklab.iol.unh.edu and io.dpdklab.iol.unh.edu > If you can provide me details of the systems you are trying to > configure, I could take a look. > > Thanks > Ajit > > On Tue, Jan 19, 2021 at 1:41 PM David Liu wrote: > > > > Hi Ajit, > > > > Thank you for helping out. > > > > How are you doing with this issue? > > > > Please let me know if you need anything information from us. > > > > Just some extra information that both Trex and dts are on the same intel > tester machine. > > > > Best, > > David > > > > On Thu, Jan 14, 2021 at 2:12 PM David Liu wrote: > >> > >> Yes, so this is the same NIC work on x86. > >> By seeing the link, I am assuming you mean the ports that are using for > Trex. If so they are UP before I start the Trex. > >> > >> Thank, > >> David > >> > >> > >> On Thu, Jan 14, 2021 at 1:11 AM Ajit Khaparde < > ajit.khaparde@broadcom.com> wrote: > >>> > >>> Does the same NIC work on x86? > >>> Also do you see link before you start the trex? I am trying to see if > the port failed to successfully come up > >>> or if there is a problem with the link. Can you check and tell? > >>> > >>> Thanks > >>> Ajit > >>> > >>> On Wed, Jan 13, 2021 at 4:20 PM David Liu wrote: > >>>> > >>>> Hi Ajit, > >>>> > >>>> Thank you for helping out. > >>>> > >>>> We have it working on the x86, but not the Arm. > >>>> > >>>> > >>>> Thanks, > >>>> David > >>>> > >>>> On Wed, Jan 13, 2021 at 5:34 PM Ajit Khaparde < > ajit.khaparde@broadcom.com> wrote: > >>>>> > >>>>> Hi David, > >>>>> I will take a look. > >>>>> Do you see similar issues on x86? I am asking because > >>>>> even I would start with that to create a baseline and then > >>>>> attempt on ARM. > >>>>> > >>>>> Thanks > >>>>> Ajit > >>>>> > >>>>> On Wed, Jan 13, 2021 at 12:08 PM David Liu wrote: > >>>>>> > >>>>>> Hi Ajit, > >>>>>> > >>>>>> We have a 25G Broadcom NIC that is installed on an Arm machine. > >>>>>> And I am running into a problem when I try to run > nic_single_core_perf on the NIC. > >>>>>> Currently, we are using: Trex v2.86 and dts from > http://git.dpdk.org/tools/dts/ > >>>>>> All the NICs are up and running when testing. > >>>>>> > >>>>>> The problem is an error when I try to run the test case inside the > nic_single_core_perf: > >>>>>> > >>>>>>> TestNicSingleCorePerf: Test running at parameters: framesize: 64, > rxd/txd: 512 > >>>>>>> dut.172.18.0.41: > x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 32,33 -n 4 > --file-prefix=dpdk_15311_20210113190237 -a 0000:93:00.0 -a 0000:93:00.1 > -- -i --portmask=0x3 --txd=512 --rxd=512 --nb-cores=1 > >>>>>>> dut.172.18.0.41: start > >>>>>>> TestNicSingleCorePerf: Test Case > test_perf_nic_single_core Result ERROR: Traceback (most recent call last): > >>>>>>> File "/opt/dts/framework/test_case.py", line 319, in > _execute_test_case > >>>>>>> case_obj() > >>>>>>> File "tests/TestSuite_nic_single_core_perf.py", line 196, in > test_perf_nic_single_core > >>>>>>> self.perf_test(self.nb_ports) > >>>>>>> File "tests/TestSuite_nic_single_core_perf.py", line 270, in > perf_test > >>>>>>> _, packets_received = > self.tester.pktgen.measure_throughput(stream_ids=streams, > options=traffic_opt) > >>>>>>> File "/opt/dts/framework/pktgen_base.py", line 245, in > measure_throughput > >>>>>>> self._prepare_transmission(stream_ids=stream_ids) > >>>>>>> File "/opt/dts/framework/pktgen_trex.py", line 778, in > _prepare_transmission > >>>>>>> self._conn.reset(ports=self._ports) > >>>>>>> File > "/opt/trex/v2.86/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py", > line 51, in wrap2 > >>>>>>> ret = f(*args, **kwargs) > >>>>>>> File > "/opt/trex/v2.86/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py", > line 339, in reset > >>>>>>> self.clear_stats(ports) > >>>>>>> File > "/opt/trex/v2.86/automation/trex_control_plane/interactive/trex/common/trex_api_annotators.py", > line 51, in wrap2 > >>>>>>> ret = f(*args, **kwargs) > >>>>>>> File > "/opt/trex/v2.86/automation/trex_control_plane/interactive/trex/stl/trex_stl_client.py", > line 1492, in clear_stats > >>>>>>> self._clear_stats_common(ports, clear_global, clear_xstats) > >>>>>>> File > "/opt/trex/v2.86/automation/trex_control_plane/interactive/trex/common/trex_client.py", > line 2876, in _clear_stats_common > >>>>>>> raise TRexError(rc) > >>>>>>> trex.common.trex_exceptions.TRexError: *** [RPC] - Failed to get > server response from tcp://172.18.0.40:4501 > >>>>>> > >>>>>> > >>>>>> I also try to run TRex in stateless mode with./t-rex-64 -i --cfg > /etc/trex_cfg.yaml and connect with ./trex-console > >>>>>> > >>>>>> Then start sending traffic with command > >>>>>>> > >>>>>>> trex>start -f stl/imix.py > >>>>>> > >>>>>> > >>>>>> But this will cause an error to turn off Trex. > >>>>>> > >>>>>>> trex> > >>>>>>> 2021-01-13 19:56:21 - [server][warning] - Server has been > shutdown - cause: 'WATCHDOG: task 'Trex DP core 1' has not responded for > more than 1.00135 seconds - timeout is 1 seconds > >>>>>>> *** traceback follows *** > >>>>>>> 1 0x561be173cf5a ./_t-rex-64(+0x19af5a) [0x561be173cf5a] > >>>>>>> 2 0x7feea3ac0980 > /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980) [0x7feea3ac0980] > >>>>>>> 3 0x561be1a05a2a rte_delay_us_block + 106 > >>>>>>> 4 0x561be16ce874 CCoreEthIF::send_burst(CCorePerPort*, > unsigned short, CVirtualIFPerSideStats*) + 3220 > >>>>>>> 5 0x561be16abf57 CCoreEthIF::flush_tx_queue() + 31 > >>>>>>> 6 0x561be171e3d9 > CNodeGenerator::handle_maintenance(CFlowGenListPerThread*) + 265 > >>>>>>> 7 0x561be171f7ec CNodeGenerator::handle_flow_sync(CGenNode*, > CFlowGenListPerThread*, bool&) + 92 > >>>>>>> 8 0x561be171fc98 > CNodeGenerator::handle_slow_messages(unsigned char, CGenNode*, > CFlowGenListPerThread*, bool) + 184 > >>>>>>> 9 0x561be16cb5f1 int CNodeGenerator::flush_file_realtime<23, > false>(double, double, CFlowGenListPerThread*, double&) + 881 > >>>>>>> 10 0x561be1905212 TrexStatelessDpCore::start_scheduler() + 226 > >>>>>>> 11 0x561be1883ae9 TrexDpCore::start() + 89 > >>>>>>> 12 0x561be1714113 > CFlowGenListPerThread::start(std::__cxx11::basic_string std::char_traits, std::allocator >&, CPreviewMode&) + 115 > >>>>>>> 13 0x561be16af8dd CGlobalTRex::run_in_core(unsigned char) + > 487 > >>>>>>> 14 0x561be16d11ad ./_t-rex-64(+0x12f1ad) [0x561be16d11ad] > >>>>>>> 15 0x561be1a1dfaa eal_thread_loop + 426 > >>>>>>> 16 0x7feea3ab56db > /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7feea3ab56db] > >>>>>>> 17 0x7feea2a8571f clone + 63 > >>>>>>> > >>>>>>> *** addr2line information follows *** > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ??:0 > >>>>>>> ' > >>>>>> > >>>>>> > >>>>>> I believe if everything is working, this should not turn off trex > but please correct me if I am wrong. > >>>>>> I wonder if you have any suggestion of how I can approach this > issue? > >>>>>> > >>>>>> Best, > >>>>>> David > >>>>>> > >>>>>> > --000000000000901e5005b9d4b6dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Ajit,
Sorry for the late reply.

You can ssh into the machine using the same VPN Username and Password= .
Can you try and see if that works?

Inf= ormatio:
- dts -=C2=A0loc= ated=C2=A0in /opt/dts
- Trex - located in /opt/trex/v2.87

- dpdk - lo= cated in /root/dpdk


Thanks,
David

On Tue, Jan 19, 2021 at 5:20 PM Ajit Khaparde <ajit.khaparde@broa= dcom.com> wrote:
Hi David,
Thanks for pinging me. Do you think I could login into the setup and
see what is happening?
I do have the credentials for two systems in your lab -
rhea.dpdklab.iol.unh.edu and io.dpdklab.iol.unh.edu
If you can provide me details of the systems you are trying to
configure, I could take a look.

Thanks
Ajit

On Tue, Jan 19, 2021 at 1:41 PM David Liu <dliu@iol.unh.edu> wrote:
>
> Hi Ajit,
>
> Thank you for helping out.
>
> How are you doing with this issue?
>
> Please let me know if you need anything information from us.
>
> Just some extra information that both Trex and dts are on the same int= el tester machine.
>
> Best,
> David
>
> On Thu, Jan 14, 2021 at 2:12 PM David Liu <dliu@iol.unh.edu> wrote:
>>
>> Yes, so this is the same NIC work on x86.
>> By seeing the link, I am assuming you mean the ports that are usin= g for Trex. If so they are UP before I start the Trex.
>>
>> Thank,
>> David
>>
>>
>> On Thu, Jan 14, 2021 at 1:11 AM Ajit Khaparde <ajit.khaparde@broadcom.com<= /a>> wrote:
>>>
>>> Does the same NIC work on x86?
>>> Also do you see link before you start the trex? I am trying to= see if the port failed to successfully come up
>>> or if there is a problem with the link. Can you check and tell= ?
>>>
>>> Thanks
>>> Ajit
>>>
>>> On Wed, Jan 13, 2021 at 4:20 PM David Liu <
dliu@iol.unh.edu> wrote:
>>>>
>>>> Hi Ajit,
>>>>
>>>> Thank you for helping out.
>>>>
>>>> We have it working on the x86, but not the Arm.
>>>>
>>>>
>>>> Thanks,
>>>> David
>>>>
>>>> On Wed, Jan 13, 2021 at 5:34 PM Ajit Khaparde <ajit.khaparde@broa= dcom.com> wrote:
>>>>>
>>>>> Hi David,
>>>>> I will take a look.
>>>>> Do you see similar issues on x86? I am asking because<= br> >>>>> even I would start with that to create a baseline and = then
>>>>> attempt on ARM.
>>>>>
>>>>> Thanks
>>>>> Ajit
>>>>>
>>>>> On Wed, Jan 13, 2021 at 12:08 PM David Liu <dliu@iol.unh.edu> wro= te:
>>>>>>
>>>>>> Hi Ajit,
>>>>>>
>>>>>> We have a 25G Broadcom NIC that is installed on an= Arm machine.
>>>>>> And I am running into a problem when I try to run = nic_single_core_perf on the NIC.
>>>>>> Currently, we are using: Trex v2.86 and dts from <= a href=3D"http://git.dpdk.org/tools/dts/" rel=3D"noreferrer" target=3D"_bla= nk">http://git.dpdk.org/tools/dts/
>>>>>> All the NICs are up and running when testing.
>>>>>>
>>>>>> The problem is an error when I try to run the test= case inside the nic_single_core_perf:
>>>>>>
>>>>>>> TestNicSingleCorePerf: Test running at paramet= ers: framesize: 64, rxd/txd: 512
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 dut.172.18.0.41: x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l = 32,33 -n 4=C2=A0 --file-prefix=3Ddpdk_15311_20210113190237=C2=A0 =C2=A0-a 0= 000:93:00.0 -a 0000:93:00.1 -- -i --portmask=3D0x3 --txd=3D512 --rxd=3D512 = --nb-cores=3D1
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 dut.172.18.0.41: start
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 TestNicSingl= eCorePerf: Test Case test_perf_nic_single_core Result ERROR: Traceback (mos= t recent call last):
>>>>>>>=C2=A0 =C2=A0File "/opt/dts/framework/test= _case.py", line 319, in _execute_test_case
>>>>>>>=C2=A0 =C2=A0 =C2=A0case_obj()
>>>>>>>=C2=A0 =C2=A0File "tests/TestSuite_nic_sin= gle_core_perf.py", line 196, in test_perf_nic_single_core
>>>>>>>=C2=A0 =C2=A0 =C2=A0self.perf_test(self.nb_port= s)
>>>>>>>=C2=A0 =C2=A0File "tests/TestSuite_nic_sin= gle_core_perf.py", line 270, in perf_test
>>>>>>>=C2=A0 =C2=A0 =C2=A0_, packets_received =3D sel= f.tester.pktgen.measure_throughput(stream_ids=3Dstreams, options=3Dtraffic_= opt)
>>>>>>>=C2=A0 =C2=A0File "/opt/dts/framework/pktg= en_base.py", line 245, in measure_throughput
>>>>>>>=C2=A0 =C2=A0 =C2=A0self._prepare_transmission(= stream_ids=3Dstream_ids)
>>>>>>>=C2=A0 =C2=A0File "/opt/dts/framework/pktg= en_trex.py", line 778, in _prepare_transmission
>>>>>>>=C2=A0 =C2=A0 =C2=A0self._conn.reset(ports=3Dse= lf._ports)
>>>>>>>=C2=A0 =C2=A0File "/opt/trex/v2.86/automat= ion/trex_control_plane/interactive/trex/common/trex_api_annotators.py"= , line 51, in wrap2
>>>>>>>=C2=A0 =C2=A0 =C2=A0ret =3D f(*args, **kwargs)<= br> >>>>>>>=C2=A0 =C2=A0File "/opt/trex/v2.86/automat= ion/trex_control_plane/interactive/trex/stl/trex_stl_client.py", line = 339, in reset
>>>>>>>=C2=A0 =C2=A0 =C2=A0self.clear_stats(ports)
>>>>>>>=C2=A0 =C2=A0File "/opt/trex/v2.86/automat= ion/trex_control_plane/interactive/trex/common/trex_api_annotators.py"= , line 51, in wrap2
>>>>>>>=C2=A0 =C2=A0 =C2=A0ret =3D f(*args, **kwargs)<= br> >>>>>>>=C2=A0 =C2=A0File "/opt/trex/v2.86/automat= ion/trex_control_plane/interactive/trex/stl/trex_stl_client.py", line = 1492, in clear_stats
>>>>>>>=C2=A0 =C2=A0 =C2=A0self._clear_stats_common(po= rts, clear_global, clear_xstats)
>>>>>>>=C2=A0 =C2=A0File "/opt/trex/v2.86/automat= ion/trex_control_plane/interactive/trex/common/trex_client.py", line 2= 876, in _clear_stats_common
>>>>>>>=C2=A0 =C2=A0 =C2=A0raise TRexError(rc)
>>>>>>> trex.common.trex_exceptions.TRexError: *** [RP= C] - Failed to get server response from tcp://172.18.0.40:4501
>>>>>>
>>>>>>
>>>>>> I also try to run TRex in stateless mode with./t-r= ex-64 -i --cfg /etc/trex_cfg.yaml and=C2=A0 connect with ./trex-console
>>>>>>
>>>>>> Then start sending traffic with command
>>>>>>>
>>>>>>> trex>start -f stl/imix.py
>>>>>>
>>>>>>
>>>>>> But this will cause an error to turn off Trex.
>>>>>>
>>>>>>> trex>
>>>>>>> 2021-01-13 19:56:21 - [server][warning]=C2=A0 = - Server has been shutdown - cause: 'WATCHDOG: task 'Trex DP core 1= ' has not responded for more than 1.00135 seconds - timeout is 1 second= s
>>>>>>> *** traceback follows ***
>>>>>>> 1=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be173cf5a ./_= t-rex-64(+0x19af5a) [0x561be173cf5a]
>>>>>>> 2=C2=A0 =C2=A0 =C2=A0 =C2=A00x7feea3ac0980 /li= b/x86_64-linux-gnu/libpthread.so.0(+0x12980) [0x7feea3ac0980]
>>>>>>> 3=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be1a05a2a rte= _delay_us_block + 106
>>>>>>> 4=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be16ce874 CCo= reEthIF::send_burst(CCorePerPort*, unsigned short, CVirtualIFPerSideStats*)= + 3220
>>>>>>> 5=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be16abf57 CCo= reEthIF::flush_tx_queue() + 31
>>>>>>> 6=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be171e3d9 CNo= deGenerator::handle_maintenance(CFlowGenListPerThread*) + 265
>>>>>>> 7=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be171f7ec CNo= deGenerator::handle_flow_sync(CGenNode*, CFlowGenListPerThread*, bool&)= + 92
>>>>>>> 8=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be171fc98 CNo= deGenerator::handle_slow_messages(unsigned char, CGenNode*, CFlowGenListPer= Thread*, bool) + 184
>>>>>>> 9=C2=A0 =C2=A0 =C2=A0 =C2=A00x561be16cb5f1 int= CNodeGenerator::flush_file_realtime<23, false>(double, double, CFlow= GenListPerThread*, double&) + 881
>>>>>>> 10=C2=A0 =C2=A0 =C2=A0 0x561be1905212 TrexStat= elessDpCore::start_scheduler() + 226
>>>>>>> 11=C2=A0 =C2=A0 =C2=A0 0x561be1883ae9 TrexDpCo= re::start() + 89
>>>>>>> 12=C2=A0 =C2=A0 =C2=A0 0x561be1714113 CFlowGen= ListPerThread::start(std::__cxx11::basic_string<char, std::char_traits&l= t;char>, std::allocator<char> >&, CPreviewMode&) + 115<= br> >>>>>>> 13=C2=A0 =C2=A0 =C2=A0 0x561be16af8dd CGlobalT= Rex::run_in_core(unsigned char) + 487
>>>>>>> 14=C2=A0 =C2=A0 =C2=A0 0x561be16d11ad ./_t-rex= -64(+0x12f1ad) [0x561be16d11ad]
>>>>>>> 15=C2=A0 =C2=A0 =C2=A0 0x561be1a1dfaa eal_thre= ad_loop + 426
>>>>>>> 16=C2=A0 =C2=A0 =C2=A0 0x7feea3ab56db /lib/x86= _64-linux-gnu/libpthread.so.0(+0x76db) [0x7feea3ab56db]
>>>>>>> 17=C2=A0 =C2=A0 =C2=A0 0x7feea2a8571f clone + = 63
>>>>>>>
>>>>>>> *** addr2line information follows ***
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> ??:0
>>>>>>> '
>>>>>>
>>>>>>
>>>>>> I believe if everything is working, this should no= t turn off trex but please correct me if I am wrong.
>>>>>> I wonder if you have any suggestion of how I can a= pproach this issue?
>>>>>>
>>>>>> Best,
>>>>>> David
>>>>>>
>>>>>>
--000000000000901e5005b9d4b6dc--