From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michael Qiu <michael.qiu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ixgbe: fix segmentation fault when start secondary process
Date: Fri, 19 Dec 2014 23:40:33 +0100 [thread overview]
Message-ID: <1810907.O11zm5mpBE@xps13> (raw)
In-Reply-To: <13515017.Dz1pkeJq4x@xps13>
2014-12-19 09:28, Thomas Monjalon:
> 2014-12-19 14:59, Michael Qiu:
> > EAL: probe driver: 8086:10fb rte_ixgbe_pmd
> > EAL: PCI memory mapped at 0x7f18c2a00000
> > EAL: PCI memory mapped at 0x7f18c2a80000
> > Segmentation fault (core dumped)
> >
> > This is introduced by commit: 46bc9d75
> > ixgbe: fix multi-process support
> > When start primary process with command line:
> > ./app/test/test -n 1 -c ffff -m 64
> > then start the second one:
> > ./app/test/test -n 1 --proc-type=secondary --file-prefix=rte
> > This segment-fault will occur.
> >
> > Root cause is test app on primary process only starts device, but
> > the queue need initialized by manually command line.
> > So the tx queue is still NULL when secondary process startup.
> >
> > Reported-by: Yong Liu <yong.liu@intel.com>
> > Signed-off-by: Michael Qiu <michael.qiu@intel.com>
> > ---
> > v2 --> v1:
> > Log clean up
>
> Clean-up failed: no need of \n in PMD_INIT_LOG ;)
>
> > + PMD_INIT_LOG(INFO, "No TX queues configured yet. "
> > + "Using default TX function\n");
Applied with above change.
Thanks
--
Thomas
prev parent reply other threads:[~2014-12-19 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 10:16 [dpdk-dev] [PATCH] " Michael Qiu
2014-12-18 10:22 ` Qiu, Michael
2014-12-18 10:27 ` De Lara Guarch, Pablo
2014-12-18 10:28 ` Bruce Richardson
2014-12-18 10:38 ` De Lara Guarch, Pablo
2014-12-19 6:59 ` [dpdk-dev] [PATCH v2] " Michael Qiu
2014-12-19 8:28 ` Thomas Monjalon
2014-12-19 22:40 ` Thomas Monjalon [this message]
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=1810907.O11zm5mpBE@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=michael.qiu@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).