You also added socket-mem which is pretty bad idea, try without.
If that doesn't help then you will need to run VPP form console and possibly 
use gdb to collect more details.

Which ARM board is that?


On 1 Feb 2018, at 14:15, adarsh m 
<addi.ada...@yahoo.in<mailto:addi.ada...@yahoo.in>> wrote:

Hi,

This is on ARM board. and yes i have modified the specific pcie address to 
added in startup.conf

 dpdk {
       socket-mem 1024
       dev 0002:f9:00.0

}


On Thursday 1 February 2018, 5:20:59 PM IST, Damjan Marion (damarion) 
<damar...@cisco.com<mailto:damar...@cisco.com>> wrote:


Please keep mailing list in CC.

Those lines doesn't show that anything is wrong...

Is this 4 socket computer? Have you modified startup.conf?


On 1 Feb 2018, at 12:40, adarsh m 
<addi.ada...@yahoo.in<mailto:addi.ada...@yahoo.in>> wrote:

Hi,

Very sorry pls check the complete one.

Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 19:37:16 vasily vpp[43454]: /usr/bin/vpp[43454]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 
0002:f9:00.0 --master-lcore 0 --socket-mem 1024,
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0002:f9:00.0 
--master-lcore 0 --socket-mem 1024,0,0,0
Feb 01 19:37:16 vasily vpp[43454]: EAL: VFIO support initialized
Feb 01 19:37:16 vasily vnet[43454]: EAL: VFIO support initialized




On Thursday 1 February 2018, 4:48:35 PM IST, Damjan Marion (damarion) 
<damar...@cisco.com<mailto:damar...@cisco.com>> wrote:



Unfortunately log you provided is incomplete and truncated so I cannot help 
much....

On 1 Feb 2018, at 11:59, adarsh m 
<addi.ada...@yahoo.in<mailto:addi.ada...@yahoo.in>> wrote:

Hi,

I checked hugepage and it was 0, so i freed this and increased it to 5120

ubuntu@vasily:~$ sudo -i
root@vasily:~# echo 5120 > /proc/sys/vm/nr_hugepages


now the previous error is not occurring when i start but VPP is not stable, 
it'll become dead after a few sceonds from start.

Logs :
ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free:     5120
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:50:46 CST; 5min ago
  Process: 42736 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42731 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42728 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42726 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42731 (code=exited, status=0/SUCCESS)

Feb 01 18:50:46 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:50:46 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:50:46 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:50:46 vasily systemd[1]: Failed to start vector packet processing 
engine.
Feb 01 18:56:12 vasily systemd[1]: Stopped vector packet processing engine.
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp start
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ 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 Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
           └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 18:56:49 vasily vpp[42866]: /usr/bin/vpp[42866]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --f
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix v
Feb 01 18:56:49 vasily vpp[42866]: EAL: VFIO support initialized
Feb 01 18:56:49 vasily vnet[42866]: EAL: VFIO support initialized
...skipping...
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
           └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 18:56:49 vasily vpp[42866]: /usr/bin/vpp[42866]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --f
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix v
Feb 01 18:56:49 vasily vpp[42866]: EAL: VFIO support initialized
Feb 01 18:56:49 vasily vnet[42866]: EAL: VFIO support initialized
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free:     2335
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:56:56 CST; 63ms ago
  Process: 42917 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42914 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42911 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42908 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42914 (code=exited, status=0/SUCCESS)

Feb 01 18:56:56 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:56:56 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:56:56 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:56:56 vasily systemd[1]: Failed to start vector packet processing 
engine.
ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free:     5120
ubuntu@vasily:~$



On Wednesday 31 January 2018, 9:30:19 PM IST, Damjan Marion (damarion) 
<damar...@cisco.com<mailto:damar...@cisco.com>> wrote:



On 31 Jan 2018, at 10:34, adarsh m via vpp-dev 
<vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> wrote:

Hi,

Pls check i am trying to bring up vpp with interface on ARM server but facing 
issue while doing so,

pls let me know if there is any existing issue or method to correct this issue.


ubuntu@vasily:~$ sudo service vpp status
[sudo] password for ubuntu:
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: enab
   Active: active (running) since Mon 2018-01-29 22:07:02 CST; 19h ago
  Process: 2461 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, status
  Process: 2453 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm /dev/shm/
 Main PID: 2472 (vpp_main)
   CGroup: /system.slice/vpp.service
           └─2472 /usr/bin/vpp -c /etc/vpp/startup.conf

Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed
Jan 29 22:07:05 vasily vnet[2472]: unix_physmem_region_iommu_register: ioctl (VF
Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed
Jan 29 22:07:05 vasily vnet[2472]: unix_physmem_region_iommu_register: ioctl (VF
Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed
Jan 29 22:07:05 vasily vnet[2472]: dpdk_ipsec_process:1011: not enough DPDK cryp
Jan 29 22:07:05 vasily vnet[2472]: dpdk_lib_init:221: DPDK drivers found no port



Looks like hugepages issue. can you show full log? What you pasted above is 
truncated...

_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev

_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev

_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev

_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to