DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jim Holland (jimholla)" <jimholla@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Mohamed Mahmoud (mmahmoud)" <mmahmoud@cisco.com>,
	"Min Tang (mtang2)" <mtang2@cisco.com>
Subject: Re: [dpdk-dev] Secondary process crash in rte_eal_init
Date: Sat, 6 Apr 2019 14:26:30 +0000	[thread overview]
Message-ID: <BN8PR11MB36348D6984E65C7AB40DF63BC8520@BN8PR11MB3634.namprd11.prod.outlook.com> (raw)
Message-ID: <20190406142630.HD9Sh74gh0ciLLB_b7hi82qG5qJRmhF3q9lTFdBe7cM@z> (raw)

Hi,

We're seeing something similar to what is described in thread below. Our product uses dpdk 17.08. Was there ever a resolution to Souvik's issue?

Thanks...Jim

On 01/04/2015 06:00, Dey, Souvik wrote:
> Hi All,
>                  We have a single primary application with multiple secondary applications launched on the same cpu core. When the system boots up for the first time ,the primary comes up followed by the secondary process everything works fine. But in between if I try to restart the secondary processes without restart the primary, the secondary process crashes with the below stack trace. Any idea what is going wrong out here.
>
> ============================================
> Stack Trace of the Crash :
> (gdb) bt
> #0 0x00007f4dad6e01b5 in raise () from /lib/libc.so.6
> #1 0x00007f4dad6e2fc0 in abort () from /lib/libc.so.6
> #2 0x0000000000402545 in __rte_panic ()
> #3 0x00000000007353f4 in rte_eal_init ()
> #4 0x0000000000403133 in main (argc=10, argv=0x7fff2c52fea8)
> ============================================
>
>
> --
> Regards,
> Souvik
>
Hi Dey,

Could you try to reproduce the issue with one of the multi-process
examples from DPDK?
Also you could provide some info such as command line options when
running both primary/secondary apps, dpdk version, etc...

Sergio

             reply	other threads:[~2019-04-06 14:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06 14:26 Jim Holland (jimholla) [this message]
2019-04-06 14:26 ` Jim Holland (jimholla)
2019-04-08  8:41 ` Burakov, Anatoly
2019-04-08  8:41   ` Burakov, Anatoly
2019-04-08 13:07   ` Mohamed Mahmoud (mmahmoud)
2019-04-08 13:07     ` Mohamed Mahmoud (mmahmoud)
2019-04-08 13:47     ` Burakov, Anatoly
2019-04-08 13:47       ` Burakov, Anatoly
  -- strict thread matches above, loose matches on Subject: below --
2015-04-01  5:00 Dey, Souvik
2015-04-03  9:13 ` Gonzalez Monroy, Sergio

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=BN8PR11MB36348D6984E65C7AB40DF63BC8520@BN8PR11MB3634.namprd11.prod.outlook.com \
    --to=jimholla@cisco.com \
    --cc=dev@dpdk.org \
    --cc=mmahmoud@cisco.com \
    --cc=mtang2@cisco.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).