On Thu, Aug 1, 2019 at 7:25 AM Takeshi T Yoshimura <t...@jp.ibm.com> wrote: > Okay. I should have set the --log-level=lib.*:debug. Here is the log. > > Starting SPDK v19.10-pre / DPDK 19.08.0-rc3 initialization... > [ DPDK EAL parameters: identify --no-shconf -c 0x1 -n 1 -m 0 > --log-level=lib.eal:6 --log-level=lib.cryptodev:5 --log-level=user1:6 > --log-level=lib.*:debug --base-virtaddr=0x200000000000 --match-allocations > --file-prefix=spdk_pid159692 ]
[snip] > EAL: No shared files mode enabled, IPC will be disabled > EAL: No shared files mode enabled, IPC is disabled > EAL: VFIO PCI modules not loaded EAL thinks that vfio kmod is not loaded at this point. > EAL: Bus pci wants IOVA as 'DC' We see no log here for the devices that are used later. - Are the (below) devices bound to vfio-pci or any other kmod at this point of the init? - Is the spdk_nvme driver loaded at this point? - I suppose forcing --iova-mode=pa resolves the issue, but can you confirm this? > EAL: Buses did not request a specific IOVA mode. > EAL: IOMMU is available, selecting IOVA as VA mode. > EAL: Module /sys/module/rte_kni not found! error 2 (No such file or directory) > EAL: Selected IOVA mode 'VA' [snip] > EAL: PCI device 0000:01:00.0 on NUMA socket 0 > EAL: probe driver: 144d:a822 spdk_nvme > EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing > EAL: Requested device 0000:01:00.0 cannot be used > EAL: PCI device 0003:01:00.0 on NUMA socket 0 > EAL: probe driver: 144d:a822 spdk_nvme > EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing > EAL: Requested device 0003:01:00.0 cannot be used > EAL: PCI device 0030:01:00.0 on NUMA socket 8 > EAL: probe driver: 144d:a822 spdk_nvme > EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing > EAL: Requested device 0030:01:00.0 cannot be used > No NVMe controllers found. -- David Marchand
