From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 2031] cn10k: NPA_POOL_ERR_INT_RANGE on Pool 1 during mbuf pool creation in testpmd
Date: Wed, 16 Sep 2026 14:02:56 +0000 [thread overview]
Message-ID: <bug-2031-3-gGuynGcjL9@https.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-2031-3@https.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=2031
Ashwin Sekhar T K (asekhar@marvell.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |asekhar@marvell.com
Status|CONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Ashwin Sekhar T K (asekhar@marvell.com) ---
PCI_BUS: Expecting 'VA' IOVA mode but current mode is 'PA', not initializing
EAL: Failed to probe device 0002:01:01.7
PCI_BUS: Expecting 'VA' IOVA mode but current mode is 'PA', not initializing
EAL: Failed to probe device 0002:01:02.0
PCI_BUS: Expecting 'VA' IOVA mode but current mode is 'PA', not initializing
EAL: Failed to probe device 0002:02:00.0
PCI_BUS: Expecting 'VA' IOVA mode but current mode is 'PA', not initializing
EAL: Failed to probe device 0002:03:00.0
PCI_BUS: Expecting 'VA' IOVA mode but current mode is 'PA', not initializing
These prints should be already coming. No further checks are required.
@Amiya,
It is not a supported mode. This means any address that you are configuring
(whether it be contexts or stacks or pointers) will run into all sorts of
issues.
You may print the pointers that you are trying to free to understand why the
Range error happened. Mostly probably there is a difference in the range
configured and the pointers being freed.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-09-16 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 19:14 [DPDK/ethdev Bug 2031] cn10k: NPA_POOL_ERR_INT_RANGE on Pool 1 during mbuf pool creation in testpmd bugzilla
2026-09-16 14:02 ` bugzilla [this message]
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-2031-3-gGuynGcjL9@https.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