mlxbf-gige: Fix kernel panic after reboot
Bug #2030765 reported by
Asmaa Mnebhi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-bluefield (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
SRU Justification:
[Impact]
Previously we fixed 2022370 by modifying the shutdown() function
but that creates a bug which needs to be reverted. It doesnt deinitialize the oob_net0 interface properly after reboot and causes issues for the UEFI OOB driver.
[Fix]
* Revert 2022370 changes
* Instead, just check that "priv" is not NULL.
[Test Case]
* Run the reboot test 1000 times
* Check that there is no kernel panic after reboot
* Check that the UEFI OOB interface gets an ip
[Regression Potential]
* We could still see a kernel panic since it is very intermittent. QA reproduced it once every 350 reboots.
CVE References
Changed in linux-bluefield (Ubuntu): | |
status: | New → Invalid |
Changed in linux-bluefield (Ubuntu Jammy): | |
status: | New → Fix Committed |
Changed in linux-bluefield (Ubuntu Focal): | |
status: | New → Fix Committed |
To post a comment you must log in.
This bug is awaiting verification that the linux-bluefield /5.15.0- 1022.24 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy' to 'verification- done-jammy' . If the problem still exists, change the tag 'verification- needed- jammy' to 'verification- failed- jammy'.
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:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!