From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 191] Sometimes timers (rte_timer) do not expire
Date: Wed, 16 Jan 2019 08:36:57 +0000 [thread overview]
Message-ID: <bug-191-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=191
Bug ID: 191
Summary: Sometimes timers (rte_timer) do not expire
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: major
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: maria.lingemark@ericsson.com
Target Milestone: ---
Created attachment 24
--> https://bugs.dpdk.org/attachment.cgi?id=24&action=edit
sample timer program
Some timers do not expire as expected. Expiry time has passed and timer is
still in state pending. Other timers installed after still expire as they
should.
Attaching a small test program that installs timers on one core and has them
expire on another to reproduce the fault.
A sample output from the program:
Installed 1000000 timers.
Warning: 4 timer(s) did not expire.
It might take a few runs to trigger the fault, and it might also be easier to
trigger with a bit of background load on the machine.
Has been reproduced on 18.05 and 18.11
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-01-16 8:36 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=bug-191-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).