[dpdk-dev] MEMNIC error at EAL : [underined symbol : per_lcore__lcore_id]

Srinivas Reddi srinivas.reddi at aricent.com
Thu Jul 17 08:10:14 CEST 2014


Hi ,
Trying to write a test app  for  MEMNIC  ...
At the EAL init I got the error  while loading the memnic driver .. ..

EAL: /usr/local/lib/librte_pmd_memnic_copy.so: undefined symbol: per_lcore__lcore_id


EAL arguments are  :

./my_memnic_app  --no-hpet  -c  7  -n 4   --porc-type=auto  -d  /usr/local/lib/librte_pmd_memnic_copy.so   -m  1024  --  -q 7 -p  f

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 0 on socket 0
EAL: Detected lcore 5 as core 1 on socket 0
EAL: Detected lcore 6 as core 2 on socket 0
EAL: Detected lcore 7 as core 3 on socket 0
EAL: Support maximum 64 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL: Auto-detected process type: PRIMARY
EAL:   cannot open VFIO container, error 2 (No such file or directory)
EAL: VFIO support could not be initialized
EAL: Setting up memory...
EAL: Ask a virtual area of 0x80000000 bytes
EAL: Virtual area found at 0x7fff40000000 (size = 0x80000000)
EAL: Requesting 1 pages of size 1024MB from socket 0
EAL: TSC frequency is ~3092836 KHz
EAL: open shared lib /usr/local/lib/librte_pmd_memnic_copy.so
EAL: /usr/local/lib/librte_pmd_memnic_copy.so: undefined symbol: per_lcore__lcore_id
EAL: Master core 0 is ready (tid=f7fe1880)
EAL: Core 2 is ready (tid=f6fa8700)
EAL: Core 1 is ready (tid=f77a9700)

Thanks and Regards,
Srinivas.

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."


More information about the dev mailing list