From: 黃致翔 <dennis5581407@gmail.com>
To: users@dpdk.org
Cc: 鄭瑞光 <crg@gapps.ntust.edu.tw>
Subject: EAL: Cannot initialize tailq: RTE_EVENT_RING
Date: Wed, 9 Mar 2022 21:13:19 +0800 [thread overview]
Message-ID: <CAO4W_V5VK+Xtbjc5RrVX573DZ3gevzjDhrBB1q266JaJ0QR4nA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3324 bytes --]
Dear all,
I try to run the application depending on v19.11 DPDK in CentOS 7.7,and I
got the error: "EAL: Cannot initialize tailq: RTE_EVENT_RING".
I don't know what kind of factor to cause this problem. Is there any
potential solution to address it?
*Here is the entire log below:*
[root@server bin]# sudo -E LD_LIBRARY_PATH=$LD_LIBRARY_PATH ./oran_5g_fapi
--cfg=oran_5g_fapi.cfg
long optsconfig file: oran_5g_fapi.cfg
init dev name: /dev/wls0
init basename: wls0
Calling rte_eal_init: ./oran_5g_fapi --proc-type=secondary --file-prefix
wls0 -w 0000:00:06.0 --iova-mode=pa
EAL: Detected 96 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/wls0/mp_socket_9789_14bf3a06701c
EAL: Selected IOVA mode 'PA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: Cannot initialize tailq: RTE_EVENT_RING
Tailq 0: qname:<VFIO_RESOURCE_LIST>, tqh_first:0x1bffe8dc0,
tqh_last:0x1bff2bdc0
Tailq 1: qname:<UIO_RESOURCE_LIST>, tqh_first:(nil), tqh_last:0x1000022b8
Tailq 2: qname:<RTE_DISTRIBUTOR>, tqh_first:(nil), tqh_last:0x1000022e8
Tailq 3: qname:<RTE_DIST_BURST>, tqh_first:(nil), tqh_last:0x100002318
Tailq 4: qname:<RTE_REORDER>, tqh_first:(nil), tqh_last:0x100002348
Tailq 5: qname:<RTE_KNI>, tqh_first:(nil), tqh_last:0x100002378
Tailq 6: qname:<RTE_HASH>, tqh_first:(nil), tqh_last:0x1000023a8
Tailq 7: qname:<RTE_FBK_HASH>, tqh_first:(nil), tqh_last:0x1000023d8
Tailq 8: qname:<RTE_LPM>, tqh_first:(nil), tqh_last:0x100002408
Tailq 9: qname:<RTE_LPM6>, tqh_first:(nil), tqh_last:0x100002438
Tailq 10: qname:<RTE_ACL>, tqh_first:(nil), tqh_last:0x100002468
Tailq 11: qname:<RTE_MBUF_DYNFLAG>, tqh_first:(nil), tqh_last:0x100002498
Tailq 12: qname:<RTE_MBUF_DYNFIELD>, tqh_first:(nil), tqh_last:0x1000024c8
Tailq 13: qname:<RTE_MEMPOOL>, tqh_first:(nil), tqh_last:0x1000024f8
Tailq 14: qname:<RTE_RING>, tqh_first:0x1bfea98c0, tqh_last:0x1bff14140
Tailq 15: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 16: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 17: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 18: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 19: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 20: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 21: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 22: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 23: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 24: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 25: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 26: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 27: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 28: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 29: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 30: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 31: qname:<>, tqh_first:(nil), tqh_last:(nil)
EAL: FATAL: Cannot init tail queues for objects
EAL: Cannot init tail queues for objects
PANIC in nr5g_fapi_dpdk_init():
Cannot init EAL
6: [./oran_5g_fapi() [0x403129]]
5: [/lib64/libc.so.6(__libc_start_main+0xf5) [0x7fdef1ae0555]]
4: [./oran_5g_fapi() [0x40348f]]
3: [./oran_5g_fapi() [0x40ed04]]
2:
[/root/intel/dpdk-19.11/x86_64-native-linuxapp-icc/lib/librte_eal.so.20.0(__rte_panic+0xc9)
[0x7fdef3f55ca9]]
1:
[/root/intel/dpdk-19.11/x86_64-native-linuxapp-icc/lib/librte_eal.so.20.0(rte_dump_stack+0x17)
[0x7fdef3f36047]]
Aborted
Best Regards,
Dennis
[-- Attachment #2: Type: text/html, Size: 3919 bytes --]
reply other threads:[~2022-03-09 13:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO4W_V5VK+Xtbjc5RrVX573DZ3gevzjDhrBB1q266JaJ0QR4nA@mail.gmail.com \
--to=dennis5581407@gmail.com \
--cc=crg@gapps.ntust.edu.tw \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).