From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id 09758803B; Wed, 9 May 2018 04:03:33 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Wed, 09 May 2018 02:03:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: testpmd X-Bugzilla-Version: 18.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vyadav@microsoft.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://dpdk.org/tracker/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 41] testpmd failed with net_failsafe error X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2018 02:03:33 -0000 https://dpdk.org/tracker/show_bug.cgi?id=3D41 Bug ID: 41 Summary: testpmd failed with net_failsafe error Product: DPDK Version: 18.05 Hardware: x86 OS: Linux Status: CONFIRMED Severity: normal Priority: Normal Component: testpmd Assignee: dev@dpdk.org Reporter: vyadav@microsoft.com Target Milestone: --- Using DPDK 18.05 RC2 on RHEL7.5 Seeing this failure when running testpmd. is this known issue in 18.05 RC2 ? [root@sivar75d5v2dpdk-1 app]# ./testpmd -w 0002:00:02.0 --vdev=3D"net_vdev_netvsc0,iface=3Deth1,force=3D1" -- -i --port-topology=3D= chained EAL: Detected 16 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/.rte_unix EAL: Probing VFIO support... EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using unreli= able clock cycles ! EAL: PCI device 0002:00:02.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 15b3:1004 net_mlx4 PMD: net_mlx4: PCI information matches, using device "mlx4_1" (VF: true) PMD: net_mlx4: 1 port(s) detected PMD: net_mlx4: port 1 MAC address is 00:0d:3a:f4:4d:53 net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) rte_pmd_tap_probe(): Initializing pmd_tap for net_tap_vsc0 as dtap0 EAL: PCI device 0003:00:02.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 15b3:1004 net_mlx4 PMD: net_mlx4: PCI information matches, using device "mlx4_2" (VF: true) PMD: net_mlx4: 1 port(s) detected PMD: net_mlx4: port 1 MAC address is 00:0d:3a:f4:48:c0 rte_pmd_tap_probe(): Initializing pmd_tap for net_tap_vsc1 as dtap1 Interactive-mode selected Warning: NUMA should be configured manually by using --port-numa-config and --ring-numa-config parameters along with --numa. testpmd: create a new mbuf pool : n=3D267456, size=3D21= 76, socket=3D0 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 1 (socket 0) net_failsafe: Rx queue offloads 0x1000 don't match port offloads 0x1000 or supported offloads 0x200e Fail to configure port 1 rx queues EAL: Error - exiting with code: 1 Cause: Start ports failed --=20 You are receiving this mail because: You are the assignee for the bug.=