DPDK usage discussions
 help / color / mirror / Atom feed
From: "Tkachuk, Georgii" <georgii.tkachuk@intel.com>
To: Lokesh Chakka <lvenkatakumarchakka@gmail.com>, users <users@dpdk.org>
Subject: RE: intel 100 Gbps Network card shutting down after enabling dpdk
Date: Mon, 1 Aug 2022 07:14:48 +0000	[thread overview]
Message-ID: <SJ0PR11MB491006F265A2630415B3513DF29A9@SJ0PR11MB4910.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CACh--sgCrJigeXLCxShXJPN6YnTbLCskxKQJBeeTLQ6Q3p1=Vw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Please check “sudo dpdk-devbind.py -s” to see if both ports are bound to vfio-pci
And some questions:

What DPDK app are you running?
What are your EAL command line arguments?
What do you mean by going down (as reported by what?)

Thank you,
Georgii

From: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
Sent: Monday, August 01, 2022 12:09 AM
To: users <users@dpdk.org>
Subject: intel 100 Gbps Network card shutting down after enabling dpdk

hello,

Recently I have bought one intel network card

https://ark.intel.com/content/www/us/en/ark/products/210969/intel-ethernet-network-adapter-e8102cqda2.html

The moment I do devbind, cards are shutting down.

$ lspci | grep -i intel
c3:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02)
c3:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02)

$ sudo dpdk-devbind.py -b vfio-pci c3:00.0 c3:00.1

After this, cards are going down. EAL is giving following error

EAL: Requested device 0000:c3:00.1 cannot be used
EAL: Error - exiting with code: 1
Cause: Error: number of ports must be even

Did anyone face this issue or anyone know how to fix the issue?

Thanks & Regards
--
Lokesh Chakka.

[-- Attachment #2: Type: text/html, Size: 4504 bytes --]

  reply	other threads:[~2022-08-01  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  7:08 Lokesh Chakka
2022-08-01  7:14 ` Tkachuk, Georgii [this message]
2022-08-01  8:20   ` Lokesh Chakka
2022-08-02  9:19     ` Van Haaren, Harry
2022-08-03  4:54       ` Lokesh Chakka

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=SJ0PR11MB491006F265A2630415B3513DF29A9@SJ0PR11MB4910.namprd11.prod.outlook.com \
    --to=georgii.tkachuk@intel.com \
    --cc=lvenkatakumarchakka@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).