DPDK usage discussions
 help / color / mirror / Atom feed
From: alex@therouter.net
To: users@dpdk.org
Subject: [dpdk-users] i40e, tx queue problem (TX descriptor is not done)
Date: Thu, 04 Jul 2019 10:12:46 +0200	[thread overview]
Message-ID: <65831ea7c78d3f754a2ca774184aa623@therouter.net> (raw)

Hi,

what could be a reason for getting "TX descriptor is not done" error on
i40e driver? My application works fine for a while, it could be day or 
couple days,
then one of tx queues would hang and stop transmitting packets while 
other tx queues
would be ok. DPDK version is 17.11.1. NIC is X710-DA2, firmware-version: 
6.01 0x80003498 0.0.0
Also, I am facing this problem only on a particular server that has a 
westmere intel cpu,
other servers are doing ok.

I already had this problem years ago and it was solved by downgrading to 
DPDK 16.x branch.
This time downgrading is not an option anymore.

Thank you.

--
Alex.

                 reply	other threads:[~2019-07-04  8:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=65831ea7c78d3f754a2ca774184aa623@therouter.net \
    --to=alex@therouter.net \
    --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).