Hi Adarsh, Trying to parse this output...
Have you tried running vpp from the workspace that it was built in instead of dealing with systemd (for now)? On 02/16 13:54:08, via Lists.Fd.Io wrote: > Hi, > > Pls check i started the vpp and found the interfaces were not detected in vpp > > so try to bind the pci with igb_uio driver and then tried to stop it but > unable to stop. > > > Logs : csit@tg:~/vpp$ sudo service vpp status > ● vpp.service - vector packet processing engine > Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: > enabled) > Active: active (running) since Fri 2018-02-16 21:02:12 CST; 2s ago > Process: 28300 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Process: 28348 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, > status=0/SUCCESS) > Process: 28344 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Main PID: 28352 (vpp_main) > Tasks: 4 > Memory: 48.0M > CPU: 187ms > CGroup: /system.slice/vpp.service > └─28352 /usr/bin/vpp -c /etc/vpp/startup.conf What does DPDK section in startup.conf look like? > Feb 16 21:02:12 tg vnet[28352]: EAL: VFIO support initialized > Feb 16 21:02:12 tg vpp[28352]: EAL: Invalid NUMA socket, default to 0 > Feb 16 21:02:12 tg vnet[28352]: EAL: Invalid NUMA socket, default to 0 > Feb 16 21:02:12 tg vnet[28352]: EAL: Cannot open > /sys/bus/pci/devices/0000:02:01.0/resource0: No such file or directory > Feb 16 21:02:12 tg vpp[28352]: EAL: Cannot open > /sys/bus/pci/devices/0000:02:01.0/resource0: No such file or directory > Feb 16 21:02:12 tg vpp[28352]: EAL: Requested device 0000:02:01.0 cannot be > used > Feb 16 21:02:12 tg vnet[28352]: EAL: Requested device 0000:02:01.0 cannot be > used > Feb 16 21:02:12 tg vnet[28352]: unix_physmem_region_iommu_register: ioctl > (VFIO_IOMMU_MAP_DMA): Invalid argument > Feb 16 21:02:12 tg vnet[28352]: dpdk_ipsec_process:1007: not enough DPDK > crypto resources, default to OpenSSL > Feb 16 21:02:12 tg vnet[28352]: dpdk_lib_init:221: DPDK drivers found no > ports... > csit@tg:~/vpp$ sudo vppctl show int > Name Idx State Counter > Count > local0 0 down > csit@tg:~/vpp$ sudo vppctl show pci > Address Sock VID:PID Link Speed Driver Product Name > Vital Product Data > 0000:02:01.0 1af4:1000 unknown uio_pci_generic > > 0000:03:01.0 1af4:1000 unknown uio_pci_generic > > 0000:04:01.0 1af4:1000 unknown uio_pci_generic > > 0000:05:01.0 1af4:1000 unknown uio_pci_generic > > 0000:06:01.0 1af4:1000 unknown uio_pci_generic > > 0000:07:01.0 1af4:1000 unknown uio_pci_generic > > > csit@tg:~/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools$ > csit@tg:~/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools$ sudo > ./dpdk-devbind.py --bind=igb_uio 0000:02:01.0 > [sudo] password for csit: > Error: bind failed for 0000:02:01.0 - Cannot bind to driver igb_uio > Error: unbind failed for 0000:02:01.0 - Cannot open > /sys/bus/pci/drivers//unbind > csit@tg:~/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools$ sudo -i > root@tg:~# cd > /home/csit/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools/ > root@tg:/home/csit/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools# > ./dpdk-devbind.py --bind=igb_uio 0000:02:01.0 > Error: bind failed for 0000:02:01.0 - Cannot bind to driver igb_uio > root@tg:/home/csit/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools# > > csit@tg:~/dpdk$ sudo service vpp status● vpp.service - vector packet > processing engine > Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: > enabled) > Active: active (running) since Fri 2018-02-16 21:02:12 CST; 23min ago > Process: 28300 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Process: 28348 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, > status=0/SUCCESS) > Process: 28344 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Main PID: 28352 (vpp_main) > Tasks: 4 > Memory: 59.6M > CPU: 4.859s > CGroup: /system.slice/vpp.service > └─28352 /usr/bin/vpp -c /etc/vpp/startup.conf > csit@tg:~/dpdk$ sudo service vpp stop > > > > > > > ^C > csit@tg:~/dpdk$ sudo service vpp stop > > > > > ^C > csit@tg:~/dpdk$ sudo service vpp status > ● vpp.service - vector packet processing engine > Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: > enabled) > Active: deactivating (stop-sigkill) (Result: timeout) since Fri 2018-02-16 > 21:25:28 CST; 2min 3s ago > Process: 28300 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Process: 28348 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, > status=0/SUCCESS) > Process: 28344 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Main PID: 28352 (vpp_main) > Tasks: 1 > Memory: 0B > CPU: 4.962s > CGroup: /system.slice/vpp.service > ‣ 28352 [vpp_main] > > Feb 16 21:25:28 tg vpp[28352]: DPDK physical memory layout: > Feb 16 21:25:28 tg vpp[28352]: Segment 0: IOVA:0x41000000, len:18874368, > virt:0xfffe86e00000, socket_id:0, hugepage_sz:2097152, nchannel:0, nr > Feb 16 21:25:28 tg vpp[28352]: Segment 1: IOVA:0x42400000, len:8388608, > virt:0xfffe86400000, socket_id:0, hugepage_sz:2097152, nchannel:0, nra > Feb 16 21:25:28 tg vpp[28352]: Segment 2: IOVA:0x43000000, len:4194304, > virt:0xfffe85e00000, socket_id:0, hugepage_sz:2097152, nchannel:0, nra > Feb 16 21:25:28 tg vpp[28352]: Segment 3: IOVA:0x43600000, len:10485760, > virt:0xfffe85200000, socket_id:0, hugepage_sz:2097152, nchannel:0, nr > Feb 16 21:25:28 tg vpp[28352]: Segment 4: IOVA:0x44400000, len:16777216, > virt:0xfffe84000000, socket_id:0, hugepage_sz:2097152, nchannel:0, nr > Feb 16 21:25:28 tg vpp[28352]: Segment 5: IOVA:0x45600000, len:6291456, > virt:0xfffe83800000, socket_id:0, hugepage_sz:2097152, nchannel:0, nra > Feb 16 21:25:28 tg vpp[28352]: Segment 6: IOVA:0x46000000, len:2097152, > virt:0xfffe83200000, socket_id:0, hugepage_sz:2097152, nchannel:0, nra > Feb 16 21:25:28 tg systemd[1]: Stopping vector packet processing engine... > Feb 16 21:26:58 tg systemd[1]: vpp.service: State 'stop-sigterm' timed out. > Killing. Do you get this same error when running vpp manually? Is there a way to see the whole log output for vpp.service? Does this show anything? > Feb 16 21:02:12 tg vnet[28352]: EAL: VFIO support initialized > Feb 16 21:02:12 tg vpp[28352]: EAL: Invalid NUMA socket, default to 0 > Feb 16 21:02:12 tg vnet[28352]: EAL: Invalid NUMA socket, default to 0 > Feb 16 21:02:12 tg vnet[28352]: EAL: Cannot open > /sys/bus/pci/devices/0000:02:01.0/resource0: No such file or directory > Feb 16 21:02:12 tg vpp[28352]: EAL: Cannot open > /sys/bus/pci/devices/0000:02:01.0/resource0: No such file or directory > Feb 16 21:02:12 tg vpp[28352]: EAL: Requested device 0000:02:01.0 cannot be > used > Feb 16 21:02:12 tg vnet[28352]: EAL: Requested device 0000:02:01.0 cannot be > used > Feb 16 21:02:12 tg vnet[28352]: unix_physmem_region_iommu_register: ioctl > (VFIO_IOMMU_MAP_DMA): Invalid argument > Feb 16 21:02:12 tg vnet[28352]: dpdk_ipsec_process:1007: not enough DPDK > crypto resources, default to OpenSSL > Feb 16 21:02:12 tg vnet[28352]: dpdk_lib_init:221: DPDK drivers found no > ports... > csit@tg:~/dpdk$ sudo service vpp stop > > > > > csit@tg:~/dpdk$ sudo service vpp status > ● vpp.service - vector packet processing engine > Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: > enabled) > Active: failed (Result: timeout) since Fri 2018-02-16 21:32:59 CST; 1min > 41s ago > Process: 28597 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Process: 28348 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, > status=0/SUCCESS) > Process: 28344 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Main PID: 28352 > Tasks: 1 > Memory: 0B > CPU: 4.964s > CGroup: /system.slice/vpp.service > ‣ 28352 [vpp_main] > > Feb 16 21:25:28 tg vpp[28352]: Segment 6: IOVA:0x46000000, len:2097152, > virt:0xfffe83200000, socket_id:0, hugepage_sz:2097152, nchannel:0, nra > Feb 16 21:25:28 tg systemd[1]: Stopping vector packet processing engine... > Feb 16 21:26:58 tg systemd[1]: vpp.service: State 'stop-sigterm' timed out. > Killing. > Feb 16 21:28:28 tg systemd[1]: vpp.service: Processes still around after > SIGKILL. Ignoring. > Feb 16 21:29:58 tg systemd[1]: vpp.service: State 'stop-post' timed out. > Terminating. > Feb 16 21:31:28 tg systemd[1]: vpp.service: State 'stop-final-sigterm' timed > out. Killing. > Feb 16 21:32:59 tg systemd[1]: vpp.service: Processes still around after > final SIGKILL. Entering failed mode. > Feb 16 21:32:59 tg systemd[1]: Stopped vector packet processing engine. > Feb 16 21:32:59 tg systemd[1]: vpp.service: Unit entered failed state. > Feb 16 21:32:59 tg systemd[1]: vpp.service: Failed with result 'timeout'. > > csit@tg:~/dpdk$ > > > Also tried to restart the vpp : > csit@tg:~/dpdk$ sudo service vpp start > csit@tg:~/dpdk$ sudo service vpp status > ● vpp.service - vector packet processing engine > Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: > enabled) > Active: deactivating (stop-sigterm) since Fri 2018-02-16 21:38:06 CST; 2s > ago > Process: 28597 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Process: 28717 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf > (code=exited, status=0/SUCCESS) > Process: 28712 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, > status=0/SUCCESS) > Process: 28710 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Main PID: 28717 (code=exited, status=0/SUCCESS) > Tasks: 1 > Memory: 0B > CPU: 130ms > CGroup: /system.slice/vpp.service > > Feb 16 21:38:06 tg vpp[28717]: /usr/bin/vpp[28717]: dpdk_config:1227: EAL > init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp > Feb 16 21:38:06 tg /usr/bin/vpp[28717]: dpdk_config:1227: EAL init args: -c 1 > -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0000:02: > Feb 16 21:38:06 tg vpp[28717]: EAL: VFIO support initialized > Feb 16 21:38:06 tg vnet[28717]: EAL: VFIO support initialized > Feb 16 21:38:06 tg vpp[28717]: EAL: Not enough memory available on socket 0! > Requested: 64MB, available: 44MB > Feb 16 21:38:06 tg vpp[28717]: EAL: FATAL: Cannot init memory > Feb 16 21:38:06 tg vpp[28717]: EAL: Cannot init memory > Feb 16 21:38:06 tg vnet[28717]: EAL: Not enough memory available on socket 0! > Requested: 64MB, available: 44MB > Feb 16 21:38:06 tg vnet[28717]: EAL: Cannot init memory > Feb 16 21:38:06 tg vpp[28717]: dpdk_config: rte_eal_init returned -1 > > csit@tg:~/dpdk$ sudo service vpp status > ● vpp.service - vector packet processing engine > Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: > enabled) > Active: deactivating (stop-sigterm) since Fri 2018-02-16 21:38:06 CST; 13s > ago > Process: 28597 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Process: 28717 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf > (code=exited, status=0/SUCCESS) > Process: 28712 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, > status=0/SUCCESS) > Process: 28710 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm > /dev/shm/vpe-api (code=exited, status=0/SUCCESS) > Main PID: 28717 (code=exited, status=0/SUCCESS) > Tasks: 1 > Memory: 0B > CPU: 130ms > CGroup: /system.slice/vpp.service > > Feb 16 21:38:06 tg vpp[28717]: /usr/bin/vpp[28717]: dpdk_config:1227: EAL > init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp > Feb 16 21:38:06 tg /usr/bin/vpp[28717]: dpdk_config:1227: EAL init args: -c 1 > -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0000:02: > Feb 16 21:38:06 tg vpp[28717]: EAL: VFIO support initialized > Feb 16 21:38:06 tg vnet[28717]: EAL: VFIO support initialized > Feb 16 21:38:06 tg vpp[28717]: EAL: Not enough memory available on socket 0! > Requested: 64MB, available: 44MB > Feb 16 21:38:06 tg vpp[28717]: EAL: FATAL: Cannot init memory > Feb 16 21:38:06 tg vpp[28717]: EAL: Cannot init memory > Feb 16 21:38:06 tg vnet[28717]: EAL: Not enough memory available on socket 0! > Requested: 64MB, available: 44MB > Feb 16 21:38:06 tg vnet[28717]: EAL: Cannot init memory > Feb 16 21:38:06 tg vpp[28717]: dpdk_config: rte_eal_init returned -1 Do you know whether hugepages are returned to the OS when you stop/kill vpp and start/launch it the next time? > csit@tg:~/dpdk$ sudo service vpp stop > ^C > csit@tg:~/dpdk$ > csit@tg:~/dpdk$ > csit@tg:~/dpdk$ > csit@tg:~/dpdk$ Brian -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8244): https://lists.fd.io/g/vpp-dev/message/8244 View All Messages In Topic (2): https://lists.fd.io/g/vpp-dev/topic/11849283 Mute This Topic: https://lists.fd.io/mt/11849283/21656 New Topic: https://lists.fd.io/g/vpp-dev/post Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656 Group Home: https://lists.fd.io/g/vpp-dev Contact Group Owner: vpp-dev+ow...@lists.fd.io Terms of Service: https://lists.fd.io/static/tos Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub -=-=-=-=-=-=-=-=-=-=-=-
