DPDK usage discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Satish Patel <satish.txt@gmail.com>
Cc: users <users@dpdk.org>, "Wang, Haiyue" <haiyue.wang@intel.com>
Subject: Re: intel X550T dpdk support issue
Date: Tue, 5 Oct 2021 08:58:59 +0200	[thread overview]
Message-ID: <CAJFAV8x85Vjuq=tbAUZ04O3wGroMyM5MOOUD=qObED8ZT_9=6Q@mail.gmail.com> (raw)
In-Reply-To: <CAPgF-fptC+fwi7gzBRmrJYnz5b1Py1RJ+Uww3HxRwrWAQcffYg@mail.gmail.com>

On Mon, Oct 4, 2021 at 8:53 PM Satish Patel <satish.txt@gmail.com> wrote:
>
> Folks,
>
> I am new to this nic series and just found a strange issue, i am sure
> people are using this nic in production with dpdk.
>
> # ovs-vsctl add-port br-vlan dpdk-1 -- set Interface dpdk-1 type=dpdk
> options:dpdk-devargs=0000:3b:00.1
> ovs-vsctl: Error detected while setting up 'dpdk-1': Error attaching
> device '0000:3b:00.1' to DPDK.  See ovs-vswitchd log for details.
> ovs-vsctl: The default log directory is "/var/log/openvswitch".
>
>
> 2021-10-04T13:20:05.751Z|00272|dpdk|ERR|EAL: Driver cannot attach the
> device (0000:3b:00.1)
> 2021-10-04T13:20:05.751Z|00273|dpdk|ERR|EAL: Failed to attach device
> on primary process
> 2021-10-04T13:20:05.751Z|00274|netdev_dpdk|WARN|Error attaching device
> '0000:3b:00.1' to DPDK
> 2021-10-04T13:20:05.751Z|00275|netdev|WARN|dpdk-1: could not set
> configuration (Invalid argument)
> 2021-10-04T13:20:05.751Z|00276|dpdk|ERR|Invalid port_id=32

Cc: ixgbe maintainer.

Let's first check if this is a OVS issue.
Can you run testpmd with this nic?



-- 
David Marchand


  parent reply	other threads:[~2021-10-05  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 18:52 Satish Patel
2021-10-04 21:20 ` Satish Patel
2021-10-05  6:54   ` David Marchand
2021-10-05  6:58 ` David Marchand [this message]
2021-10-21 13:59   ` Satish Patel

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='CAJFAV8x85Vjuq=tbAUZ04O3wGroMyM5MOOUD=qObED8ZT_9=6Q@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=haiyue.wang@intel.com \
    --cc=satish.txt@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).