Public bug reported:
SRU Justification:
[Impact]
* The oob_net0 interface, managed by the mlxbf_gige driver, will be
up and enabled but can stop processing received packets if three
specific conditions occur:
1) driver has received more than (N * RxRingSize) packets but less
than (N+1 * RxRingSize) packets where N is an odd number.
Note: the command "ethtool -g oob_net0" will display the current
receive ring size, which currently defaults to 128.
2) the driver's interface was disabled via "ifconfig oob_net0 down"
during the window described in #1.
3) the driver's interface is re-enabled via "ifconfig oob_net0 up"
Without this fix, the driver needs to be unloaded and re-loaded
to correct this condition.
[Fix]
* The fix is to ensure that the driver's "valid_polarity" field
is cleared during the open() method so that it always matches
the receive polarity used by hardware.
[Test Case]
* To test this fix, need to send in a specific number of packets to
the "oob_net0" interface, then issue "ifconfig oob_net0 down" to
disable the interface. A subsequent "ifconfig oob_net0 up" command
will succesfully bring up the "oob_net0" interface and start the
processing of received packets.
[Regression Potential]
* There is low risk of this fix causing any problems.
[Other]
* The mlxbf_gige driver will display v1.25 in modinfo after these changes.
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
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/1942932
Title:
oob_net0 up but stops processing Rx packets
Status in linux-bluefield package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
* The oob_net0 interface, managed by the mlxbf_gige driver, will be
up and enabled but can stop processing received packets if three
specific conditions occur:
1) driver has received more than (N * RxRingSize) packets but less
than (N+1 * RxRingSize) packets where N is an odd number.
Note: the command "ethtool -g oob_net0" will display the current
receive ring size, which currently defaults to 128.
2) the driver's interface was disabled via "ifconfig oob_net0 down"
during the window described in #1.
3) the driver's interface is re-enabled via "ifconfig oob_net0 up"
Without this fix, the driver needs to be unloaded and re-loaded
to correct this condition.
[Fix]
* The fix is to ensure that the driver's "valid_polarity" field
is cleared during the open() method so that it always matches
the receive polarity used by hardware.
[Test Case]
* To test this fix, need to send in a specific number of packets to
the "oob_net0" interface, then issue "ifconfig oob_net0 down" to
disable the interface. A subsequent "ifconfig oob_net0 up" command
will succesfully bring up the "oob_net0" interface and start the
processing of received packets.
[Regression Potential]
* There is low risk of this fix causing any problems.
[Other]
* The mlxbf_gige driver will display v1.25 in modinfo after these changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+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
