From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1427] BPF jit test errors on Arm
Date: Tue, 30 Apr 2024 18:04:27 +0000 [thread overview]
Message-ID: <bug-1427-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1427
Bug ID: 1427
Summary: BPF jit test errors on Arm
Product: DPDK
Version: 24.03
Hardware: ARM
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
In test log, saw these errors in BPF JIT when running bpf_convert_autotest.
Looks like bug in ARM JIT that is being silently ignored.
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probe PCI driver: net_virtio (1af4:1041) device: 0000:01:00.0 (socket -1)
eth_virtio_pci_init(): Failed to init PCI device
EAL: Requested device 0000:01:00.0 cannot be used
APP: HPET is not enabled, using TSC as default timer
BPF: bpf_exec(0xffff87fc2000): division by 0 at pc: 0x68;
BPF: emit(0xffff87fc2000): invalid opcode 0x30 at pc: 1;
BPF: __rte_bpf_jit(0xffff87fc2000) failed, error code: -22;
BPF: emit(0xffff87fc2000): invalid opcode 0x30 at pc: 1;
BPF: __rte_bpf_jit(0xffff87fc2000) failed, error code: -22;
BPF: emit(0xffff87fc2000): invalid opcode 0x30 at pc: 1;
BPF: __rte_bpf_jit(0xffff87fc2000) failed, error code: -22;
-------
9/111 DPDK:fast-tests / bpf_convert_autotest OK 0.28 s
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3426 bytes --]
reply other threads:[~2024-04-30 18:04 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-1427-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 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 read-only IMAP folder(s) and NNTP newsgroup(s).