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 13:50:00 -0600 [thread overview]
Message-ID: <56AA70E8.3070302@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?
Yes, we're going through a switch. It's been pretty intermittent, so
reproducing on demand is difficult.
> Likewise it might be interesting to try the OoT driver, just to see if a
> later fix addressed what you're seeing. I can't think of anything off the
> top of my head, but trying the newer driver might help identify if we have.
Right, I'll bring it up.
> Also are you seeing anything interesting on the system log?
No, pretty boring.
Chris
next prev parent reply other threads:[~2016-01-28 19:50 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 [this message]
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=56AA70E8.3070302@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.