From: Chris Friesen <chris.friesen@windriver.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] anyone aware of problem with 82599ES stuck sending TX pause frames?
Date: Thu, 28 Jan 2016 12:40:33 -0600 [thread overview]
Message-ID: <56AA60A1.7060408@windriver.com> (raw)
Hi,
We're running linux 3.10 with the 3.13.10-k ixgbe driver. We're seeing an
intermittent issue with our 82599ES devices where they seem to occasionally get
stuck sending TX pause frames.
controller-1:~$ sudo ethtool -S eth26 | grep flow_control
tx_flow_control_xon: 0
rx_flow_control_xon: 0
tx_flow_control_xoff: 3446364
rx_flow_control_xoff: 0
[wrsroot at controller-1 ~(keystone_admin)]$ sudo ethtool -S eth6 | grep flow_control
tx_flow_control_xon: 103
rx_flow_control_xon: 0
tx_flow_control_xoff: 9174310
rx_flow_control_xoff: 0
Generally it seems to happen after receiving a relatively small number of
packets (though the data set is small so this may be chance):
13: eth4.85 at eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc htb state UP
mode DEFAULT
link/ether 90:e2:ba:37:9b:ec brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
96681 212 0 0 0 192
TX: bytes packets errors dropped carrier collsns
77054616 136387 0 0 0 0
29: eth26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP mode
DEFAULT qlen 1000
link/ether 90:e2:ba:4f:9e:38 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
105471 213 0 0 0 129291
TX: bytes packets errors dropped carrier collsns
49801840 88058 0 0 0 0
ifdown/ifup seems to be sufficient to cause it to start behaving normally again.
Anyone seen anything like this?
Thanks,
Chris
next reply other threads:[~2016-01-28 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 18:40 Chris Friesen [this message]
2016-01-28 18:53 ` [Intel-wired-lan] anyone aware of problem with 82599ES stuck sending TX pause frames? Chris Friesen
2016-01-28 19:13 ` Skidmore, Donald C
2016-01-28 19:50 ` Chris Friesen
2016-02-01 15:05 ` Chris Friesen
2016-02-01 17:54 ` Skidmore, Donald C
[not found] ` <56AFF0BB.1030309@windriver.com>
2016-02-02 3:01 ` Skidmore, Donald C
2016-02-02 3:05 ` Legacy, Allain
2016-02-05 21:47 ` Legacy, Allain
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=56AA60A1.7060408@windriver.com \
--to=chris.friesen@windriver.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.