** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2022387
Title:
mlxbf-gige: Fix intermittent no ip issue
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Focal:
New
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.
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2022387/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
