From: Nishant Verma <vnish11@gmail.com>
To: USERS <users@dpdk.org>
Cc: dev@dpdk.org
Subject: Crash in RTE_TIMER
Date: Thu, 15 Sep 2022 08:06:16 -0400 [thread overview]
Message-ID: <CAHhCjUEc+GY-Ni39Xj1WKLTxT+n=KojWuGS=6os11YzTKUTVsQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2547 bytes --]
Hi,
I am facing one issue in rte_timer. The description is quite generic.
*Setup*:
I am using DPDK 21.11
OS: Centos 7.9
CPU: Intel(R) Xeon(R) CPU D-1581 @ 1.80GHz
NIC: SR-IOV on X552
Process: Single primary process(one core, one instance) only
*Earlier Running Application: *
We built our app as a library and used that lib while building the DPDK
app.
For example:
We have some c source code that we build libMY_APP.a This library was
included in an application that is using DPDK libs as well. Consider this
application as an extension to the l3fwd app present in the example
section. It works well. [BINARY = DPDK_APP(l3fwd based app) + libMY_APP.a ]
*Changed APP:*
Now instead of our my_app as library, we build DPDK app as static lib and
include that lib plus rte libs while compiling my_app.
Compilation and everything is fine but don't know why rte_timer_mange
always crashed out.
[BINARY = DPDK_APP compile as static lib(libL3DPDK.a) + (librte_*.a) +
MY_APP(source code) ]
*Extract from gdb core dump*
0x00000000060db2ae in timer_get_prev_entries (time_val=17207637256614021,
tim_lcore=1, prev=0x7fffffffe100, priv_timer=0x5bfe20980)
at ../lib/timer/rte_timer.c:364
364 prev[lvl]->sl_next[lvl]->expire <=
time_val)
Missing separate debuginfos, use: debuginfo-install
boost-system-1.53.0-27.el7.x86_64 glibc-2.17-260.el7.x86_64
libgcc-4.8.5-36.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64
numactl-libs-2.0.9-7.el7.x86_64 openssl-libs-1.0.2k-16.el7.x86_64
zlib-1.2.7-18.el7.x86_64
(gdb) bt
#0 0x00000000060db2ae in timer_get_prev_entries
(time_val=17207637256614021, tim_lcore=1, prev=0x7fffffffe100,
priv_timer=0x5bfe20980)
at ../lib/timer/rte_timer.c:364
#1 0x00000000060db41f in timer_add (tim=0x4bbe54200, tim_lcore=1,
priv_timer=0x5bfe20980) at ../lib/timer/rte_timer.c:406
#2 0x00000000060db8f8 in __rte_timer_reset (tim=0x4bbe54200,
expire=17207637256614021, period=1170000000, tim_lcore=1,
fct=0x6fbc7c <SKL_timerExpired>, arg=0x730f200 <g_healthCheckTimer>,
local_is_locked=0, timer_data=0x5bfe20980)
at ../lib/timer/rte_timer.c:531
#3 0x00000000060dba42 in rte_timer_alt_reset (timer_data_id=0,
tim=0x4bbe54200, ticks=1170000000, type=PERIODICAL, tim_lcore=1,
fct=0x6fbc7c <SKL_timerExpired>, arg=0x730f200 <g_healthCheckTimer>) at
../lib/timer/rte_timer.c:574
#4 0x00000000060db99b in rte_timer_reset (tim=0x4bbe54200,
ticks=1170000000, type=PERIODICAL, tim_lcore=1
Any pointer or suggestion, anything needs to be checked is highly
appreciated.
Thanks.
Nishant
[-- Attachment #2: Type: text/html, Size: 5570 bytes --]
reply other threads:[~2022-09-15 12:06 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='CAHhCjUEc+GY-Ni39Xj1WKLTxT+n=KojWuGS=6os11YzTKUTVsQ@mail.gmail.com' \
--to=vnish11@gmail.com \
--cc=dev@dpdk.org \
--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).