** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-bluefield (Ubuntu Focal)
Assignee: (unassigned) => David Thompson (dthompso-98)
** 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/1989495
Title:
mlxbf_gige: need to clear MDIO gateway lock after read
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Focal:
In Progress
Bug description:
SRU Justification:
[Impact]
The BlueField-2 GIGE logic accesses the MDIO device via reads/writes
to a gateway (GW) register. The MDIO GW lock is set after read. Make
sure to always clear to indicate that the GW register is not being used.
If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO
accesses will be blocked and PHY device will be inaccessible.
[Fix]
For each MDIO read and write transaction, the last step should
be to clear the MDIO GW lock.
[Test Case]
Boot the BlueField-2 platform
Bring up the "oob_net0" interface via DHCP or static IP
Ping and file transfer over "oob_net0" should work properly
Bounce the "oob_net0" interface a few times and repeat tests
[Regression Potential]
* Low risk for causing a regression, tested well in our lab.
[Other]
* None
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989495/+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
