DPDK usage discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: gowrishankar <gowrishankar.m@linux.vnet.ibm.com>, users@dpdk.org
Subject: Re: [dpdk-users] Difficulty With rte_eal_init()
Date: Wed, 30 Mar 2016 15:40:31 -0700	[thread overview]
Message-ID: <20160330224031.GA23525@mhcomputing.net> (raw)
In-Reply-To: <CA+Gp1nYTbO8o+MtTizYtkx6+3vJaOibp8rtF0JTnWVXNETOL7Q@mail.gmail.com>

On Wed, Mar 30, 2016 at 07:16:28AM -0700, Cliff Burdick wrote:
> Thanks, -march=native fixed that. Now I get a segfault when calling
> rte_eth_tx_queue_setup:
> 
> PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7fff755efa40
> hw_ring=0x7fff755efe80 dma_addr=0x2005befe80
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff6798aad in malloc_consolidate () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> glibc-2.17-106.el7_2.4.x86_64 libconfig-1.4.9-5.el7.x86_64
> libgcc-4.8.5-4.el7.x86_64 libstdc++-4.8.5-4.el7.x86_64

Rebuild your DPDK w/ "-g -O0" in the EXTRA_CFLAGS env var. Install the 
libc6-dbg symbols or equivalent. The BT is useless w/ no symbols.

Matthew.

      reply	other threads:[~2016-03-30 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 21:45 Cliff Burdick
2016-03-18 21:56 ` Matthew Hall
2016-03-18 23:40   ` Cliff Burdick
2016-03-19  2:45     ` Matthew Hall
2016-03-20  6:16 ` gowrishankar
2016-03-29 21:16   ` Cliff Burdick
2016-03-29 21:30     ` Matthew Hall
2016-03-30  7:49       ` Van Haaren, Harry
2016-03-30 14:16       ` Cliff Burdick
2016-03-30 22:40         ` Matthew Hall [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=20160330224031.GA23525@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=gowrishankar.m@linux.vnet.ibm.com \
    --cc=shaklee3@gmail.com \
    --cc=users@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).