From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 259] unable to run sample t3 as bpf-load for testpmd
Date: Tue, 30 Apr 2019 04:53:47 +0000 [thread overview]
Message-ID: <bug-259-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=259
Bug ID: 259
Summary: unable to run sample t3 as bpf-load for testpmd
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: major
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
NIC:
L: PCI device 0000:08:00.0 on NUMA socket 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI memory mapped at 0x1500a00000
EAL: PCI memory mapped at 0x1501200000
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI memory mapped at 0x1501208000
EAL: PCI memory mapped at 0x1501a08000
CMD:
a) ./app/testpmd -l 3,4,5 --log-level=eal,8 --log-level=lib.bpf,8
--legacy-mem -- -i --portmask=0x3 --port-topology=chained
--total-num-mbufs=4096
b) bpf-load rx 0 0 J ../test/bpf/t3.o
Error:
bpf-load rx 0 0 J ../test/bpf/t3.o
validate: invalid src-reg field at pc: 10
rte_bpf_elf_load(fname="../test/bpf/t3.o", sname=".text") failed, error code:
22
-22:Invalid argument
testpmd> bpf-load rx 0 0 M ../test/bpf/t3.o
validate: invalid src-reg field at pc: 10
rte_bpf_elf_load(fname="../test/bpf/t3.o", sname=".text") failed, error code:
22
-22:Invalid argument
testpmd> bpf-load rx 0 0 B ../test/bpf/t3.o
unknown flag: 'B'validate: invalid src-reg field at pc: 10
rte_bpf_elf_load(fname="../test/bpf/t3.o", sname=".text") failed, error code:
22
-22:Invalid argument
testpmd> bpf-load rx 0 0 - ../test/bpf/t3.o
unknown flag: 'B'validate: invalid src-reg field at pc: 10
rte_bpf_elf_load(fname="../test/bpf/t3.o", sname=".text") failed, error code:
22
-22:Invalid argument
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-04-30 4:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-259-3@http.bugs.dpdk.org/ \
--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.