From: Samudrala, Sridhar <sridhar.samudrala@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] ixgbe Tx Unit Hangs seen when l2-fwd-offload is enabled
Date: Tue, 03 May 2016 16:16:07 -0700 [thread overview]
Message-ID: <57293137.3070404@intel.com> (raw)
In-Reply-To: <26D9FDECA4FBDD4AADA65D8E2FC68A4A0F9D57D1@ORSMSX104.amr.corp.intel.com>
On 5/3/2016 2:13 PM, Bowers, AndrewX wrote:
> It still does it even with the latest tree pulled, however if I create the macvlan, bring it up, and THEN enable l2-fwd-offload, I don't get the tx hang. If I try to create another macvlan with l2-fwd-offload enabled, I get the tx hang.
Yes. I too see this issue even with the latest tree.
I remember not seeing this issue with 4.6.0-rc1 based tree.
>> -----Original Message-----
>> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org] On
>> Behalf Of Jeff Kirsher
>> Sent: Tuesday, May 03, 2016 1:35 PM
>> To: Samudrala, Sridhar <sridhar.samudrala@intel.com>; intel-wired-
>> lan at lists.osuosl.org
>> Subject: Re: [Intel-wired-lan] ixgbe Tx Unit Hangs seen when l2-fwd-offload
>> is enabled
>>
>> On Tue, 2016-05-03 at 10:58 -0700, Samudrala, Sridhar wrote:
>>> With the latest davem's next-next or Jeff's dev-queue branch (4.6.0-
>>> rc5+), I am seeing Tx Unit Hangs when
>>> using offloaded macvlans.
>>>
>>> Here is a simple sequence of commands that can reproduce this issue.
>>> ethtool -K p4p1 l2-fwd-offload on
>>> ip link add link p4p1 name mvlan_1 type macvlan
>>> ip link set mvlan_1 up
>>>
>>> Here is the kernel log when this happens.
>>>
>>> May 03 10:45:01 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: NIC Link is Up
>>> 10 Gbps, Flow Control: RX/TX
>>> May 03 10:45:01 sri02 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): p4p1:
>>> link becomes ready
>>> May 03 10:45:30 sri02 kernel: ixgbe 0000:1f:00.0: removed PHC on p4p1
>>> May 03 10:45:30 sri02 kernel: ixgbe 0000:1f:00.0: Multiqueue Enabled:
>>> Rx Queue count = 2, Tx Queue count = 2 May 03 10:45:30 sri02 kernel:
>>> ixgbe 0000:1f:00.0 p4p1: Could not enable Tx Queue 0 May 03 10:45:30
>>> sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Could not enable Tx Queue 2 May
>>> 03 10:45:30 sri02 kernel: ixgbe 0000:1f:00.0: registered PHC device on
>>> p4p1 May 03 10:45:30 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: detected
>>> SFP+:
>>> 5
>>> May 03 10:45:31 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: NIC Link is Up
>>> 10 Gbps, Flow Control: RX/TX
>>> May 03 10:45:33 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Detected Tx
>>> Unit Hang
>>> Tx Queue <0>
>>> TDH, TDT <0>, <4>
>>> next_to_use <4>
>>> next_to_clean <0>
>>> tx_buffer_info[next_to_clean]
>>> time_stamp <10005560a>
>>> jiffies <100055df4> May
>>> 03 10:45:33 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: tx hang 1 detected
>>> on queue 0, resetting adapter May 03 10:45:33 sri02 kernel: ixgbe
>>> 0000:1f:00.0 p4p1: initiating reset due to tx timeout May 03 10:45:33
>>> sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Reset adapter May 03 10:45:35
>>> sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Could not enable Tx Queue 0 May
>>> 03 10:45:35 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Could not enable Tx
>>> Queue 2 May 03 10:45:35 sri02 kernel: ixgbe 0000:1f:00.0 p4p1:
>>> detected SFP+:
>>> 5
>>> May 03 10:45:36 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: NIC Link is Up
>>> 10 Gbps, Flow Control: RX/TX
>>> May 03 10:45:38 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Detected Tx
>>> Unit Hang
>>> Tx Queue <0>
>>> TDH, TDT <0>, <2>
>>> next_to_use <2>
>>> next_to_clean <0>
>>> tx_buffer_info[next_to_clean]
>>> time_stamp <1000569a0>
>>> jiffies <1000571b0> May
>>> 03 10:45:38 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: tx hang 2 detected
>>> on queue 0, resetting adapter May 03 10:45:38 sri02 kernel: ixgbe
>>> 0000:1f:00.0 p4p1: initiating reset due to tx timeout May 03 10:45:38
>>> sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Reset adapter May 03 10:45:40
>>> sri02 kernel: Virtual device mvlan_1 asks to queue packet!
>>> May 03 10:45:40 sri02 kernel: ixgbe 0000:1f:00.0 p4p1: Could not
>>> enable Tx Queue 0 May 03 10:45:40 sri02 kernel: ixgbe 0000:1f:00.0
>>> p4p1: Could not enable Tx Queue 2
>> I just updated my tree with Dave's latest just now, so if you want to re-pull
>> and see if it still exists, please.
prev parent reply other threads:[~2016-05-03 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 17:58 [Intel-wired-lan] ixgbe Tx Unit Hangs seen when l2-fwd-offload is enabled Samudrala, Sridhar
2016-05-03 20:34 ` Jeff Kirsher
2016-05-03 21:13 ` Bowers, AndrewX
2016-05-03 23:16 ` Samudrala, Sridhar [this message]
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=57293137.3070404@intel.com \
--to=sridhar.samudrala@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.