From: David Marchand <david.marchand@redhat.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: Aaron Conole <aconole@redhat.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] service: stop lcore threads before 'finalize'
Date: Mon, 10 Feb 2020 15:42:21 +0100 [thread overview]
Message-ID: <CAJFAV8ycnzSut_Ud0DwFuVv1+ztehc_=romUTBoJ8jC5unPeWw@mail.gmail.com> (raw)
In-Reply-To: <MN2PR11MB4447E9C17B3505FFC271EBD7D7190@MN2PR11MB4447.namprd11.prod.outlook.com>
On Mon, Feb 10, 2020 at 3:16 PM Van Haaren, Harry
<harry.van.haaren@intel.com> wrote:
> I haven't easily reproduced this yet - so I'll investigate a way to
> reproduce with close to 100% rate, then we can identify the root cause
> and actually get a clean fix. If you have pointers to reproduce easily,
> please let me know.
- In shell #1:
$ git reset --hard v20.02-rc2
HEAD is now at 2636c2a23 version: 20.02-rc2
$ rm -rf build
$ git diff
diff --git a/app/test/meson.build b/app/test/meson.build
index 3675ffb5c..23c00a618 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -400,7 +400,7 @@ timeout_seconds = 600
timeout_seconds_fast = 10
get_coremask = find_program('get-coremask.sh')
-num_cores_arg = '-l ' + run_command(get_coremask).stdout().strip()
+num_cores_arg = '-l 0,1'
test_args = [num_cores_arg]
foreach arg : fast_test_names
$ meson --werror --buildtype=debugoptimized build
The Meson build system
Version: 0.47.2
Source dir: /home/dmarchan/dpdk
Build dir: /home/dmarchan/dpdk/build
Build type: native build
Program cat found: YES (/usr/bin/cat)
Project name: DPDK
Project version: 20.02.0-rc2
...
$ ninja-build -C build
ninja: Entering directory `build'
[2081/2081] Linking target app/test/dpdk-test.
$ taskset -pc 1 $$
pid 11143's current affinity list: 0-7
pid 11143's new affinity list: 1
$ while true; do true; done
- Now, in shell #2, as root:
# taskset -pc 0,1 $$
pid 22233's current affinity list: 0-7
pid 22233's new affinity list: 0,1
# meson test --gdb --repeat=10000 service_autotest
...
+ ------------------------------------------------------- +
+ Test Suite Summary
+ Tests Total : 16
+ Tests Skipped : 3
+ Tests Executed : 16
+ Tests Unsupported: 0
+ Tests Passed : 13
+ Tests Failed : 0
+ ------------------------------------------------------- +
Test OK
RTE>>
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4922700 (LWP 31194)]
rte_service_runner_func (arg=<optimized out>) at
../lib/librte_eal/common/rte_service.c:453
453 cs->loops++;
A debugging session is active.
Inferior 1 [process 31187] will be killed.
Quit anyway? (y or n)
I get the crash in like 30s, often less.
In my test right now, I got the crash on the 3rd try.
--
David Marchand
next prev parent reply other threads:[~2020-02-10 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 19:50 Aaron Conole
2020-01-17 8:17 ` David Marchand
2020-02-04 13:34 ` David Marchand
2020-02-04 14:50 ` Aaron Conole
2020-02-10 14:16 ` Van Haaren, Harry
2020-02-10 14:42 ` David Marchand [this message]
2020-02-20 13:25 ` David Marchand
2020-02-21 12:28 ` Van Haaren, Harry
2020-03-10 13:04 ` David Marchand
2020-03-10 13:27 ` Van Haaren, Harry
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='CAJFAV8ycnzSut_Ud0DwFuVv1+ztehc_=romUTBoJ8jC5unPeWw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
/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).