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: Mon, 1 Feb 2016 09:05:47 -0600 [thread overview]
Message-ID: <56AF744B.1000403@windriver.com> (raw)
In-Reply-To: <F6FB0E698C9B3143BDF729DF2228664691E709B9@ORSMSX116.amr.corp.intel.com>
On 01/28/2016 01:13 PM, Skidmore, Donald C wrote:
> Hey Chris,
>
> I've seen issues that seemed similar to this caused by a switches not playing
> well with the NIC. Are you going through a switch and if so could you see if
> you can recreate back to back with a different switch?
Got some more information on this from one of our guys. Here's what he says:
"This has been seen at least 3 times recently... on 3 different switches (1 of
which is a Cisco Nexus 5K). I would be willing to believe that our Quanta
switches did something suspect, but not the Cisco. I also find it hard to
believe that something the switch could do would cause the device to send out
pause frames. As far as I understand it is only supposed to do that in response
to running out of rx buffers while receiving packets. It is then supposed to
send XON frames once more rx buffers are available.
I checked the switch ports connected to both systems that were affected today.
Neither of them have flow control enabled which means this was the Intel device
doing something suspect all on its own."
I'll see about trying the out-of-tree driver, but without a straightforward way
to reproduce it'll be hard to tell if it fixes things.
Chris
next prev parent reply other threads:[~2016-02-01 15:05 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
2016-01-28 19:13 ` Skidmore, Donald C
2016-01-28 19:50 ` Chris Friesen
2016-02-01 15:05 ` Chris Friesen [this message]
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=56AF744B.1000403@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