From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 539] [dpdk-20.11] distributor/test_multiple_ports: Failed to map pci BAR4 only in SLES15_SP1
Date: Wed, 23 Sep 2020 02:05:43 +0000 [thread overview]
Message-ID: <bug-539-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=539
Bug ID: 539
Summary: [dpdk-20.11] distributor/test_multiple_ports: Failed
to map pci BAR4 only in SLES15_SP1
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: weix.ling@intel.com
Target Milestone: ---
--------------------------------reproduce
steps-----------------------------------
1.bind pci to dpdk driver
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:81:00.0 0000:81:00.1
2.start dpdk-distributor
x86_64-native-linuxapp-gcc/examples/dpdk-distributor -c 0xfc00 -n 4 -w
0000:81:00.0 -w 0000:81:00.1 -- -p 0x3
3.ouput
# linux-4fr6:~/dpdk # x86_64-native-linuxapp-gcc/examples/dpdk-distributor -c
0xfc00 -n 4 -w 0000:81:00.0 -w 0000:81:00.1 -- -p 0x3
EAL: Detected 40 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found
for that size
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: using IOMMU type 1 (Type 1)
EAL: Failed to map pci BAR4
EAL: 0000:81:00.0 mapping BAR4 failed: Success
EAL: Requested device 0000:81:00.0 cannot be used
EAL: Failed to map pci BAR4
EAL: 0000:81:00.1 mapping BAR4 failed: Success
EAL: Requested device 0000:81:00.1 cannot be used
EAL: Bus (pci) probe failed.
EAL: No legacy callbacks, legacy socket not created
POWER: Env isn't set yet!
POWER: Attempting to initialise ACPI cpufreq power management...
POWER: Initialized successfully for lcore 11 power management
POWER: Initialized successfully for lcore 12 power management
POWER: Initialized successfully for lcore 13 power management
POWER: Initialized successfully for lcore 14 power management
POWER: Initialized successfully for lcore 15 power management
EAL: Error - exiting with code: 1
Cause: Error: no ethernet ports detected
4.expected result
# It run normally.
Regression
5.bad commit
Is this issue a regression: (Y)
Version the regression was introduced: e200535c1ca382c518da810ab484e3f0660d351d
[root@localhost dpdk]# git show e200535c1ca382c518da810ab484e3f0660d351d
commit e200535c1ca382c518da810ab484e3f0660d351d (HEAD)
Author: David Marchand <david.marchand@redhat.com>
Date: Thu Sep 17 13:28:21 2020 +0200
mem: drop mapping API workaround
Now that the pci_map_resource API is private to the PCI bus, we can drop
the compatibility workaround we had implemented in 20.08.
Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-09-23 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 2:05 bugzilla [this message]
2020-09-28 10:10 ` [dpdk-dev] [Bug 539] [dpdk-20.11] distributor/test_multiple_ports: Failed to map pci BAR4 only in SLES15_SP1 bugzilla
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-539-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.