mlxbf-gige: Fix intermittent no ip issue
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-bluefield (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Committed
|
Medium
|
Asmaa Mnebhi | ||
Bug Description
SRU Justification:
[Impact]
Although the link is up, and the PHY interrupt is cleared, there is no ip assigned. Nothing is being transmitted, and nothing is received. The RX error count keeps on increasing (check ifconfig oob_net0). After several minutes, the RX error count stagnates and the oob finally gets an ip and is pingable.
[Fix]
The issue is in the mlxbf_gige_rx_init function. As soon as the RX DMA is enabled,
the RX CI reaches the max 128, it becomes equal to RX PI. And RX CI doesn't decrease
since the code hasn't ran phy_start yet. The solution is to move the rx init after phy_start.
This fix applies to both 5.4 and 5.15.
[Test Case]
* Check if the gige driver is loaded
* Check that the oob_net0 interface is up and pingable from an external host
* Do at ~1000 resets and powercycles and check the oon_net0 interface again
[Regression Potential]
* No known regressions.
| Changed in linux-bluefield (Ubuntu Focal): | |
| assignee: | nobody → Asmaa Mnebhi (asmaam) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| Changed in linux-bluefield (Ubuntu): | |
| status: | New → Invalid |
| Changed in linux-bluefield (Ubuntu Jammy): | |
| assignee: | nobody → Asmaa Mnebhi (asmaam) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| no longer affects: | linux-bluefield (Ubuntu Focal) |
| Changed in linux-bluefield (Ubuntu Jammy): | |
| status: | In Progress → Fix Committed |
| Bartlomiej Zolnierkiewicz (bzolnier) wrote | #1 |
| tags: | added: verification-needed-jammy |
| tags: |
added: verification-done-jammy removed: verification-needed-jammy |
This bug is awaiting verification that the linux-bluefield
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/