Hoi, VPP does not run on that board, because the soc does not enumerate its DPDK enabled interfaces on the PCIe bus, but rather has a custom bus, which VPP is not integrated with. Incidentally, I did get VPP itself to run but without DPDK (or AVF or etc) interfaces; and its basic functionality (ie create loop, tunnel, tap) did seem to work, just no accelerated interfaces. There were also issues with the 25G and 100G ports on the serdes, it seemed to only want to run 8x10G.
Ben also had a few insights on my previous post to vpp-dev@ list: https://lists.fd.io/g/vpp-dev/message/21984 groet, Pim On Thu, Dec 1, 2022 at 12:59 PM <agv...@gmail.com> wrote: > Dear VPP community, > > > I'm trying to operate VPP on SolidRun LX2160 board, which is based on 16 > cores A72 NXP SoC, unfortunately, with little success. Does anybody have > any experience with running VPP on such boards? > > > The performance in my tests is quite good (more then 4mpps NDR) , but VPP > works very unstable and segfaults in time interval from seconds to hours > after start. > The events causing segfaults were not identified. It may happen (and > usually) when you walk through CLI. It may happen (less frequently) when > just forwarding packets without a touch to vppctl. Applying config longer > then few lines usually cause that. Second VPPCTL connection usually couses > that, > > I was trying the following versions of VPP with literally same results: > > - VPP 21.01 from LSDK distribution, built on the board natively > - VPP 22.10, from Master branch, crossbuilt using > https://docs.nxp.com/bundle/GUID-87AD3497-0BD4-4492-8040-3F3BE0F2B087/page/GUID-8A75A4AD-2EB9-4A5A-A784-465B98E67951.html > - VPP 22.08, built using flexbuild tool (from same link above). > > I was trying different settings of main_heap memory pool (size, pagesize), > different hugepages settings (standard 4k, huge 2M, huge 1G), but there > were no serious improvement. It looks like 22.08 most stable and may last > for few hours. > > As performance looks promising, I'm really looking forward to make it work > stable. Can somebody please advice , where do I need to look at to fix > the problem? There are , according to CSIT, good results on other ARM v8 > platforms. > As for OS, I'm using pre-built Ubuntu Core-based distribution from > SolidRun. > > See below OS information, logs with crash. See in attachement: Platform > dmesg and GDB trace of 22.10 crash. > Below are system logs of VPP crashes. > > abramov@nc2s5:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=20.04 > DISTRIB_CODENAME=focal > DISTRIB_DESCRIPTION="Ubuntu 20.04.5 LTS" > abramov@nc2s5:~$ uname -a > Linux nc2s5 5.10.35-00018-gbb124648d42c #1 SMP PREEMPT Wed May 11 17:07:05 > UTC 2022 aarch64 aarch64 aarch64 GNU/Linux > abramov@nc2s5:~$ > > > Dec 01 10:35:42 nc2s5 vnet[2259]: received signal SIGSEGV, PC unsupported, > faulting address 0x2d3ba50a885 > Dec 01 10:35:42 nc2s5 vnet[2259]: #0 0x0000ffffa7df2e2c 0xffffa7df2e2c > Dec 01 10:35:42 nc2s5 vnet[2259]: #1 0x0000ffffa95ad588 0xffffa95ad588 > Dec 01 10:35:42 nc2s5 vnet[2259]: #2 0x0000ffffa7da0090 > vlib_node_runtime_sync_stats + 0x0 > Dec 01 10:35:42 nc2s5 vnet[2259]: #3 0x0000ffffa7da191c > vlib_node_sync_stats + 0x4c > Dec 01 10:35:42 nc2s5 vnet[2259]: #4 0x0000ffffa7dd973c > vlib_worker_thread_barrier_release + 0x45c > Dec 01 10:35:42 nc2s5 vnet[2259]: #5 0x0000ffffa7de6ef4 0xffffa7de6ef4 > Dec 01 10:35:42 nc2s5 vnet[2259]: #6 0x0000ffffa7de827c 0xffffa7de827c > Dec 01 10:35:42 nc2s5 vnet[2259]: #7 0x0000ffffa7df00dc 0xffffa7df00dc > Dec 01 10:35:42 nc2s5 vnet[2259]: #8 0x0000ffffa7da5e04 vlib_main + 0x8f4 > Dec 01 10:35:42 nc2s5 vnet[2259]: #9 0x0000ffffa7df1d8c 0xffffa7df1d8c > Dec 01 10:35:42 nc2s5 vnet[2259]: #10 0x0000ffffa7c36f8c clib_calljmp + > 0x24 > > Dec 01 10:26:56 nc2s5 vnet[2232]: received signal SIGSEGV, PC unsupported, > faulting address 0x208 > Dec 01 10:26:56 nc2s5 vnet[2232]: #0 0x0000ffffa4bebe2c 0xffffa4bebe2c > Dec 01 10:26:56 nc2s5 vnet[2232]: #1 0x0000ffffa63a6588 0xffffa63a6588 > Dec 01 10:26:56 nc2s5 vnet[2232]: #2 0x0000ffffa6340aa8 0xffffa6340aa8 > Dec 01 10:26:56 nc2s5 vnet[2232]: #3 0x0000ffffa4b9f150 vlib_main + 0xc40 > Dec 01 10:26:56 nc2s5 vnet[2232]: #4 0x0000ffffa4bead8c 0xffffa4bead8c > Dec 01 10:26:56 nc2s5 vnet[2232]: #5 0x0000ffffa4a2ff8c clib_calljmp + > 0x24 > > > -- Pim van Pelt <p...@ipng.nl> PBVP1-RIPE - http://www.ipng.nl/
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22265): https://lists.fd.io/g/vpp-dev/message/22265 Mute This Topic: https://lists.fd.io/mt/95379828/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
