From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>
Subject: RE: [PATCH] net/intel: do not bypass mbuf lib for mbuf fast-free
Date: Sun, 19 Apr 2026 08:29:08 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F657FD@smartserver.smartshare.dk> (raw)
In-Reply-To: <20260418095639.10003-1-mb@smartsharesystems.com>
Recheck-request: iol-unit-amd64-testing
FYI, the log from the failure:
54/143 DPDK:fast-tests / eal_flags_misc_autotest FAIL 1.21s (exit status 255 or signal 127 SIGinvalid)
>>> DPDK_TEST=eal_flags_misc_autotest MALLOC_PERTURB_=27 /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --file-prefix=eal_flags_misc_autotest
-------------------------------------------------------------------------- --------------------------------------------------------------------------
[...]
Calling recursive action for test_misc_flags
Returned from recursive action for test_misc_flags with 0
Cleaning up /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test recursive instance
/root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test recursive instance returning 0
Running binary with argv[]:'/root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test' '--file-prefix=virtaddr' '--log-level=lib.eal:debug' '--no-pci' '--base-virtaddr=0x23456789'
EAL: lib.eal log level changed from info to debug
EAL: Detected lcore 0 as core 0 on NUMA node 0
EAL: Detected lcore 1 as core 0 on NUMA node 0
EAL: Detected lcore 2 as core 0 on NUMA node 0
EAL: Detected lcore 3 as core 0 on NUMA node 0
EAL: Detected lcore 4 as core 0 on NUMA node 0
EAL: Detected lcore 5 as core 0 on NUMA node 0
EAL: Detected lcore 6 as core 0 on NUMA node 0
EAL: Detected lcore 7 as core 0 on NUMA node 0
EAL: Detected lcore 8 as core 0 on NUMA node 1
EAL: Detected lcore 9 as core 0 on NUMA node 1
EAL: Detected lcore 10 as core 0 on NUMA node 1
EAL: Detected lcore 11 as core 0 on NUMA node 1
EAL: Detected lcore 12 as core 0 on NUMA node 1
EAL: Detected lcore 13 as core 0 on NUMA node 1
EAL: Detected lcore 14 as core 0 on NUMA node 1
EAL: Detected lcore 15 as core 0 on NUMA node 1
EAL: Maximum logical cores by configuration: 128
EAL: Detected CPU lcores: 16
EAL: Detected NUMA nodes: 2
EAL: Cores selected by affinity auto-detection: 0
EAL: lcore 0 mapped to physical core 0
EAL: Control threads will use cores: 0
EAL: Checking presence of .so 'librte_eal.so.26.2'
EAL: Checking presence of .so 'librte_eal.so.26'
EAL: Checking presence of .so 'librte_eal.so'
EAL: Detected static linkage of DPDK
EAL: Ask a virtual area of 0x7000 bytes
EAL: Cannot get a virtual area at requested address: 0x23ff9000 (got 0x7fa029a47000)
EAL: Cannot mmap memory for rte_config
EAL: Cannot init config
EAL: rte_intr_fd_get, ln 209: Interrupt instance unallocated
EAL: Unregistering with invalid input parameter
Error with EAL initialization, ret = -1
Error (line 1101) - process did not run ok with --base-virtaddr parameter
Test Failed
RTE>>
next prev parent reply other threads:[~2026-04-19 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 9:56 [PATCH] net/intel: do not bypass mbuf lib for mbuf fast-free Morten Brørup
2026-04-19 6:29 ` Morten Brørup [this message]
2026-04-21 10:34 ` Bruce Richardson
2026-04-21 10:44 ` Morten Brørup
2026-04-21 11:00 ` Bruce Richardson
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=98CBD80474FA8B44BF855DF32C47DC35F657FD@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--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