From: Neil Horman <nhorman@tuxdriver.com>
To: "Saha, Avik (AWS)" <aviksaha@amazon.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK 1.7 crashes on table initialization
Date: Wed, 24 Sep 2014 06:08:36 -0400 [thread overview]
Message-ID: <20140924100836.GB4446@hmsreliant.think-freely.org> (raw)
In-Reply-To: <A4A7819F3AE089479B8A88B97202C75D37BE7C62@ex10-mbx-9001.ant.amazon.com>
On Wed, Sep 24, 2014 at 09:37:07AM +0000, Saha, Avik (AWS) wrote:
> I am not getting a useful core -
> I just get the error message -PIPELINE: rte_pipeline_table_create: Table creation failed on the command line
>
> So I played around with the action_data_size and for some reason, the application comes up fine if it I specify it as sizeof(struct rtre_pipeline_table_entry). Sorry I do not have any more detail but is there any way I can debug this?
>
> Avik
>
Attach GDB to it then and break on that error log call. Then we can see what
the f_create method is pointing too and figure out what type of table create is
failing.
Neil
> -----Original Message-----
> From: Neil Horman [mailto:nhorman@tuxdriver.com]
> Sent: Tuesday, September 23, 2014 3:21 AM
> To: Saha, Avik (AWS)
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] DPDK 1.7 crashes on table initialization
>
> On Tue, Sep 23, 2014 at 09:07:55AM +0000, Saha, Avik (AWS) wrote:
> > Hey guys
> > My DPDK application is crashing on a table creation when I specify .action_data_size as greater than 0. I could not find the constraints on this field in documentation (multiple of 4 or something). Could someone please give some guidance on this issue.
> >
> Post the backtrace when the error occurs?
> Neil
>
> > Thanks
> > Avik
> >
>
prev parent reply other threads:[~2014-09-24 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 9:07 Saha, Avik (AWS)
2014-09-23 10:21 ` Neil Horman
2014-09-24 9:37 ` Saha, Avik (AWS)
2014-09-24 10:08 ` Neil Horman [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=20140924100836.GB4446@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=aviksaha@amazon.com \
--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).