DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jose Gavine Cueto <pepedocs@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] intel x540-at2
Date: Fri, 3 Jan 2014 18:31:37 +0800	[thread overview]
Message-ID: <CAJ5bv6H06N0tXb+8kzBsTHcg1TaW57FL_wC0iys6ZhXywW=h4A@mail.gmail.com> (raw)
In-Reply-To: <201401031126.10063.thomas.monjalon@6wind.com>

I haven't added it yet, because as of the moment I do not have an access to
the built DPDK library I was using.  I was just linking it with my DPDK
application.

I tried to debug it with GDB and disassembled it, the invalid instruction
was "vzeroupper" which occurs at rte_eal_init, somewhere when initializing
pthreads.

Ok, I'll to debug more and get more information.

Thanks again,
Pepe


On Fri, Jan 3, 2014 at 6:26 PM, Thomas Monjalon
<thomas.monjalon@6wind.com>wrote:

> 03/01/2014 11:09, Jose Gavine Cueto :
> > I am running a DPDK application in a guest VM which uses one VF.  This VM
> > runs on top of the host that has an x540-at2 NIC and uses the ixgbe
> driver.
> >  The issue was that every time I run the DPDK application in the VM it
> > errors an invalid instruction and stops there.
>
> First, have you added x540-at2 in ixgbe_type.h, ixgbe_api.c and
> rte_pci_dev_ids.h ?
> What is the invalid instruction ? Have you tried to debug it ?
>
> I don't know this NIC so I'm afraid you should debug it by yourself.
>
> Please, keep us informed if you make it working.
> --
> Thomas
>



-- 
To stop learning is like to stop loving.

  reply	other threads:[~2014-01-03 10:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  9:18 Jose Gavine Cueto
2014-01-02 14:24 ` Thomas Monjalon
2014-01-03  9:09   ` Jose Gavine Cueto
2014-01-03  9:16     ` Jose Gavine Cueto
2014-01-03  9:56       ` Thomas Monjalon
2014-01-03 10:09         ` Jose Gavine Cueto
2014-01-03 10:26           ` Thomas Monjalon
2014-01-03 10:31             ` Jose Gavine Cueto [this message]
2014-01-03 13:43               ` Venkatesan, Venky
2014-01-03 13:59                 ` Thomas Monjalon
2014-01-05 14:31                 ` Jose Gavine Cueto
2014-01-05 14:54                   ` Thomas Monjalon
2014-01-06  6:03                     ` Jose Gavine Cueto
2014-01-08  6:13                       ` Jose Gavine Cueto

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='CAJ5bv6H06N0tXb+8kzBsTHcg1TaW57FL_wC0iys6ZhXywW=h4A@mail.gmail.com' \
    --to=pepedocs@gmail.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).