thunder nic: RX_PACKET_DIS fix regression with Extreme Networks switch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
Xenial |
Triaged
|
High
|
Unassigned | ||
Yakkety |
Won't Fix
|
High
|
Unassigned | ||
Zesty |
Triaged
|
High
|
Unassigned |
Bug Description
Upstream backport [3] introduced a regression with ThunderX nodes (CRB-1S, CRB-2S) and our 10G switch (Extreme Networks x670 10GE L3).
We have opened a downstream bug report [1], where we temporarily bypassed this by pinning the kernel to 4.4.0-45.
I also tested 4.8 (multiple builds), 4.10 and 4.11-rc1 (vanilla); all are still affected by link training issues with our switch, with 4.11-rc1 not working at all and reporting more issues (logs attached in a different LP comment [2]).
I also confirmed that reverting the commit in questions fixes the issues in our setup (tested on top of 4.10.0-13 linux-image-
BR,
Alex
[1] https:/
[2] https:/
[3] https:/
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
tags: | added: kernel-da-key |
Changed in linux (Ubuntu Yakkety): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Yakkety): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → High |
tags: | added: xenial yakkety zesty |
Changed in linux (Ubuntu Xenial): | |
status: | Confirmed → Triaged |
Changed in linux (Ubuntu Yakkety): | |
status: | Confirmed → Triaged |
Changed in linux (Ubuntu Zesty): | |
status: | Confirmed → Triaged |
Let me know if I should attach any logs, although there are *no* traces anywhere, at least with default log levels (without recompiling).