DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: [dpdk-dev] Debugging EAL PCI / Driver Init
Date: Fri, 1 Aug 2014 10:51:38 -0700	[thread overview]
Message-ID: <20140801175138.GA31733@mhcomputing.net> (raw)

Hello,

I am running into a problem where Eth driver init works fine in a sample app 
and finds my NICs, and the NICs appear in rte_eal_pci_dump(stdout) but they 
don't show up in rte_eth_dev_count() even after rte_eal_pci_probe() is called 
the same as the sample apps, so my app won't boot.

I have a lot of experience using the older versions of the DPDK where you had 
to call the PMD init functions manually but no experience with the later 
versions where the DPDK is supposed to init the PMDs itself automatically.

What do I have to do to dump the most possible debug output on why the driver 
list for my PCI devices always seems empty? Any places I should look to see 
the issue? Maybe I didn't link it together with the right DPDK libs? I used 
the combined DPDK static lib libintel_dpdk.a to make things simpler as I had 
seen recommended in various places.

Thanks,
Matthew.

             reply	other threads:[~2014-08-01 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 17:51 Matthew Hall [this message]
2014-08-02 15:29 ` Matthew Hall
2014-08-02 15:43   ` Matthew Hall
     [not found]     ` <CAFLKUzKOPxC4jQBG6C07QXJ=MrcydxG9FdHD6h7omj6BY=99LQ@mail.gmail.com>
2014-08-02 16:46       ` Matthew Hall
2014-08-03 10:38         ` Alex Markuze
2014-08-03 11:41           ` Alex Markuze
2014-08-03 17:23             ` Matthew Hall
2014-08-03 18:13               ` Jayakumar, Muthurajan
2014-08-03 21:39                 ` Matthew Hall

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=20140801175138.GA31733@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --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).