From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1844] BPF elf test failing on RHEL8
Date: Sun, 30 Nov 2025 18:26:58 +0000 [thread overview]
Message-ID: <bug-1844-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1844
Bug ID: 1844
Summary: BPF elf test failing on RHEL8
Product: DPDK
Version: 25.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Testing 25.11 with RHEL 8.8 VM.
EAL: Detected CPU lcores: 4
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'
VIRTIO_INIT: eth_virtio_pci_init(): Failed to init PCI device
PCI_BUS: Requested device 0000:01:00.0 cannot be used
APP: HPET is not enabled, using TSC as default timer
BPF: bpf_exec(0x7ff5b6355000): division by 0 at pc: 0x68;
------------------------------------------------------------------------------
10/86 DPDK:fast-tests / bpf_elf_autotest FAIL 0.12s
(exit status 255 or signal 127 SIGinvalid)
18:21:23 MALLOC_PERTURB_=40 DPDK_TEST=bpf_elf_autotest
/home/shemminger/DPDK/main/build/app/dpdk-test --no-huge -m 2048
----------------------------------- output -----------------------------------
stdout:
RTE>>bpf_elf_autotest^M
test_bpf_elf_load: ELF load test passed
test_bpf_elf_tx_load start
bpf_tx_test@3541: failed to load BPF filter from file=/tmp/dpdk_bpf_tx_gl71ik.o
error=22:(Invalid argument)
Test Failed
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-11-30 18:27 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-1844-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.