netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nikita V. Shirokov" <tehnerd@tehnerd.com>
To: netdev@vger.kernel.org
Cc: alexander.h.duyck@intel.com, jeffrey.t.kirsher@intel.com
Subject: ixgbe hangs when XDP_TX is enabled
Date: Mon, 20 Aug 2018 12:31:08 -0700	[thread overview]
Message-ID: <20180820193108.GA6390@maindev> (raw)

we are getting such errors:

[  408.737313] ixgbe 0000:03:00.0 eth0: Detected Tx Unit Hang (XDP)
                 Tx Queue             <46>
                 TDH, TDT             <0>, <2>
                 next_to_use          <2>
                 next_to_clean        <0>
               tx_buffer_info[next_to_clean]
                 time_stamp           <0>
                 jiffies              <1000197c0>
[  408.804438] ixgbe 0000:03:00.0 eth0: tx hang 1 detected on queue 46, resetting adapter
[  408.804440] ixgbe 0000:03:00.0 eth0: initiating reset due to tx timeout
[  408.817679] ixgbe 0000:03:00.0 eth0: Reset adapter
[  408.866091] ixgbe 0000:03:00.0 eth0: TXDCTL.ENABLE for one or more queues not cleared within the polling period
[  409.345289] ixgbe 0000:03:00.0 eth0: detected SFP+: 3
[  409.497232] ixgbe 0000:03:00.0 eth0: NIC Link is Up 10 Gbps, Flow Control: RX/TX

while running XDP prog on ixgbe nic.
right now i'm seing this on bpfnext kernel 
(latest commit from Wed Aug 15 15:04:25 2018 -0700 ;
9a76aba02a37718242d7cdc294f0a3901928aa57)

looks like this is the same issue as reported by Brenden in
https://www.spinics.net/lists/netdev/msg439438.html

             reply	other threads:[~2018-08-20 22:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 19:31 Nikita V. Shirokov [this message]
2018-08-21 15:58 ` ixgbe hangs when XDP_TX is enabled Alexander Duyck
2018-08-21 16:58   ` Nikita V. Shirokov
2018-08-21 18:13     ` Alexander Duyck
2018-08-22 16:22       ` Jeff Kirsher
2018-08-24 14:25         ` Jesper Dangaard Brouer

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=20180820193108.GA6390@maindev \
    --to=tehnerd@tehnerd.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.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).