* [dpdk-dev] [Bug 41] testpmd failed with net_failsafe error
@ 2018-05-09 2:03 bugzilla
2018-05-09 8:02 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2018-05-09 2:03 UTC (permalink / raw)
To: dev
https://dpdk.org/tracker/show_bug.cgi?id=41
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="net_vdev_netvsc0,iface=eth1,force=1" -- -i --port-topology=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=yes nonstop_tsc=no -> using unreliable
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 <mbuf_pool_socket_0>: n=267456, size=2176,
socket=0
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
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-dev] [Bug 41] testpmd failed with net_failsafe error
2018-05-09 2:03 [dpdk-dev] [Bug 41] testpmd failed with net_failsafe error bugzilla
@ 2018-05-09 8:02 ` bugzilla
0 siblings, 0 replies; 2+ messages in thread
From: bugzilla @ 2018-05-09 8:02 UTC (permalink / raw)
To: dev
https://dpdk.org/tracker/show_bug.cgi?id=41
Raslan Darawsheh (rasland@mellanox.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
CC| |rasland@mellanox.com
Resolution|--- |FIXED
--- Comment #1 from Raslan Darawsheh (rasland@mellanox.com) ---
Hi,
this is already a known issue in MLX4 and we already have a patch to fix it.
please try applying this patch before running it.
https://dpdk.org/dev/patchwork/patch/39461/
Kindest regards
Raslan Darawsheh
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-05-09 8:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-09 2:03 [dpdk-dev] [Bug 41] testpmd failed with net_failsafe error bugzilla
2018-05-09 8:02 ` bugzilla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).