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:53:29 -0600 [thread overview]
Message-ID: <56AA63A9.7050005@windriver.com> (raw)
In-Reply-To: <56AA60A1.7060408@windriver.com>
On 01/28/2016 12:40 PM, Chris Friesen wrote:
> 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
For what it's worth, on this same device the dropped/missed counts are
relatively low:
rx_errors: 0
rx_dropped: 0
rx_no_buffer_count: 0
rx_missed_errors: 160553
tx_flow_control_xon: 0
rx_flow_control_xon: 0
tx_flow_control_xoff: 3446364
rx_flow_control_xoff: 0
rx_csum_offload_errors: 0
alloc_rx_page_failed: 0
alloc_rx_buff_failed: 0
rx_no_dma_resources: 0
Chris
next prev parent reply other threads:[~2016-01-28 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 18:40 [Intel-wired-lan] anyone aware of problem with 82599ES stuck sending TX pause frames? Chris Friesen
2016-01-28 18:53 ` Chris Friesen [this message]
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=56AA63A9.7050005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox