From: Vincent Li <vincent.mc.li@gmail.com>
To: Archit Pandey <architpandeynitk@gmail.com>
Cc: users@dpdk.org, "Mohit P. Tahiliani" <tahiliani@nitk.edu.in>,
Tarun Anand <anandtarun2@gmail.com>,
sanjana.krishnam@gmail.com
Subject: Re: [dpdk-users] Cannot set link up after binding with igb_uio
Date: Thu, 9 Jan 2020 10:21:01 -0800 [thread overview]
Message-ID: <CAK3+h2wF2xdWmq7LBE2_DTDWr3rVpWEcHeWyRtyr9nNy3uYvNQ@mail.gmail.com> (raw)
In-Reply-To: <CANtWViNWFCRpLSjkkhxwpbgmCeg+_oqKVWh8sGVrcX10_3pOBg@mail.gmail.com>
On Thu, Jan 9, 2020 at 5:43 AM Archit Pandey <architpandeynitk@gmail.com> wrote:
>
> Hello team,
>
> Weirdly this issue gets resolved upon resetting the NICs. Which has led me
> to believe that the problem lies in how the NICs are configured. I'm
> working with Intel x701 NIC with the i40e driver. By any chance is this a
> known issue with these NICs or driver?
>
how did you reset the NIC? could you please be more specific? there is
fix for ixgbe link status from searching driver commit log, but not
for i40e driver. could you recompile the dpdk with
CONFIG_RTE_LIBRTE_ETHDEV_DEBUG=y ? it is in
<path-to-dpdk>/x86_64-native-linuxapp-gcc/.config
re-insert the igb_uio, re-bind the NIC after enabling the DEBUG.
you can also try using vfio other than igb_uio
> I have tried upgrading my i40e driver to the recommended version v2.9.21
> for dpdk 19.11, however that did not work.
did any previous dpdk version work other than dpdk 19.11 ?
>
>
> I would really appreciate help in debugging this issue.
>
usually more detail/steps you provided would be helpful to
troubleshoot the issue
next prev parent reply other threads:[~2020-01-09 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 17:17 Archit Pandey
2020-01-09 13:42 ` Archit Pandey
2020-01-09 18:21 ` Vincent Li [this message]
2020-01-13 8:18 ` Muhammad Zain-ul-Abideen
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=CAK3+h2wF2xdWmq7LBE2_DTDWr3rVpWEcHeWyRtyr9nNy3uYvNQ@mail.gmail.com \
--to=vincent.mc.li@gmail.com \
--cc=anandtarun2@gmail.com \
--cc=architpandeynitk@gmail.com \
--cc=sanjana.krishnam@gmail.com \
--cc=tahiliani@nitk.edu.in \
--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).