Public bug reported:

SRU Justification:

[Impact]

At the moment, the OOB port is enabled in the mlxbf_gige_probe
function. If the mlxbf_gige_open is not executed, this could cause
pause frames to increase in the case where there is high backgroud
traffic. This results in clogging the BMC port as well.

[Fix]

* Move enabling the OOB port to mlxbf_gige_open.

[Test Case]

* Main test for this bug: Check that the BMC is always pingable while
pushing a BFB

Other tests:
* Check if the gige driver is loaded
* Check that the oob_net0 interface is up and operational
* Do the reboot test and powercycle test and check the oob_net0 interface again
* Push BFB multiple times and make sure the OOB is up and running

[Regression Potential]

Since are moving code that hasn't moved since BF2, it is important to make sure 
that there is no regression.
Make sure that the OOB interface is always up and pingable after the reboot 
test, the powercycle test
and after pushing a BFB.

** 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/2035128

Title:
  mlxbf-gige: Enable the OOB port in mlxbf_gige_open

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  At the moment, the OOB port is enabled in the mlxbf_gige_probe
  function. If the mlxbf_gige_open is not executed, this could cause
  pause frames to increase in the case where there is high backgroud
  traffic. This results in clogging the BMC port as well.

  [Fix]

  * Move enabling the OOB port to mlxbf_gige_open.

  [Test Case]

  * Main test for this bug: Check that the BMC is always pingable while
  pushing a BFB

  Other tests:
  * Check if the gige driver is loaded
  * Check that the oob_net0 interface is up and operational
  * Do the reboot test and powercycle test and check the oob_net0 interface 
again
  * Push BFB multiple times and make sure the OOB is up and running

  [Regression Potential]

  Since are moving code that hasn't moved since BF2, it is important to make 
sure that there is no regression.
  Make sure that the OOB interface is always up and pingable after the reboot 
test, the powercycle test
  and after pushing a BFB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035128/+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

Reply via email to