Hi, Replaying here because I can't find the first email in the thread.
Regarding testing results with Mellanox devices, we did basic functional testing with testpmd, and don't see any issues. Testing matrix: - NIC: ConnectX-5 / OS: RHEL 7.4 / Kernel: 5.3.0 / Driver: rdma-core v25.1 / fw: 16.26.1040 - NIC: ConnectX-4 Lx / OS: RHEL 7.4 / Kernel: 5.3.0 / Driver: rdma-core v25.1 / fw: 14.26.1040 - NIC: ConnectX-5 / OS: RHEL 7.4 / Kernel: 3.10.0-693.el7.x86_64 / Driver: MLNX_OFED_LINUX-4.7-1.0.0.1 / fw: 16.26.1040 - NIC: ConnectX-4 Lx / OS: RHEL 7.4 / Kernel: 3.10.0-693.el7.x86_64 / Driver: MLNX_OFED_LINUX-4.7-1.0.0.1 / fw: 14.26.1040 I apologize for the delay in reporting our results. Thanks, Ali > -----Original Message----- > From: Christian Ehrhardt <christian.ehrha...@canonical.com> > Sent: Thursday, October 17, 2019 4:55 PM > To: Abhishek Marathe <abhishek.mara...@microsoft.com> > Cc: Kevin Traynor <ktray...@redhat.com>; Ju-Hyoung Lee > <juh...@microsoft.com>; sta...@dpdk.org; dev@dpdk.org; Akhil Goyal > <akhil.go...@nxp.com>; Ali Alnubani <alia...@mellanox.com>; > benjamin.wal...@intel.com; David Christensen <d...@linux.vnet.ibm.com>; > Hemant Agrawal <hemant.agra...@nxp.com>; Ian Stokes > <ian.sto...@intel.com>; Jerin Jacob <jer...@marvell.com>; John McNamara > <john.mcnam...@intel.com>; Luca Boccassi <bl...@debian.org>; Pei Zhang > <pezh...@redhat.com>; pingx...@intel.com; qian.q...@intel.com; Raslan > Darawsheh <rasl...@mellanox.com>; Thomas Monjalon > <tho...@monjalon.net>; yuan.p...@intel.com; zhaoyan.c...@intel.com > Subject: Re: [dpdk-dev] [dpdk-stable] 18.11.3 (LTS) patches review and test > > Azure image: 'Canonical UbuntuServer 18.04-DAILY-LTS latest': > > > > * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED > > * VERIFY-DPDK-OVS: PASSED > > * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED > > * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED > > * PERF-DPDK-MULTICORE-PPS-F32: FAILED > > Hi Abhishek, > since you use the daily LTS image and see such a significant change compared > to before, could it by any chance be that this made you switch from kernel > 4.15 to 5.0. > Because by the normal HWE policy [1] this got into Bionic rebuilds and it > seems [2] the same is true for linux-azure kernel flavours. > > Could you check your logs if the kernel version changed between the old and > the new runs? > An alternative might be to rerun 18.11.2 to see if it drops as well, which > might > indicate that it wasn't 18.11.2 -> 18.11.3 but something else like the kernel. > > Not sure if that old kernel is ok, but you always can go back to what a > version > was released with. So in this case package linux-azure=4.15.0.1009.9 is still > there and you could try > 18.11.3 with that maybe? > > Let me know if you need help changing kernels there. > > [1]: <removed> > [2]: <removed>
