distributor/test_multiple_ports: Failed to map pci BAR4 only in SLES15_SP1
[email protected]
Acked-by Andrew Rybchenkohttps://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: [email protected]
Reporter: [email protected]
Target Milestone: ---
--------------------------------reproduce steps-----------------------------------
1.bind pci to dpdk driverusertools/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 <[email protected]>
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.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugs.dpdk.org/show_bug.cgi?id=539
lingwei ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED--- Comment #3 from lingwei ([email protected]) --- Verified patchset http://patches.dpdk.org/patch/78968/ on baseline f5d6738c2ec10170b0e03eb9ff95544be0559641.
Tested-by on sageville/SLES15-SP1
https://mails.dpdk.org/archives/dev/2020-September/183166.html
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.