From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 41] testpmd failed with net_failsafe error
Date: Wed, 09 May 2018 02:03:32 +0000 [thread overview]
Message-ID: <bug-41-3@http.dpdk.org/tracker/> (raw)
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.
next reply other threads:[~2018-05-09 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 2:03 bugzilla [this message]
2018-05-09 8:02 ` [Bug 41] testpmd failed with net_failsafe error bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-41-3@http.dpdk.org/tracker/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.