Open SalDaniele opened 11 months ago
thillux
commented
8 months ago We also experienced such behavior with the current master_devel branch of the upcoming 4.26 release. Do you plan to fix this with 4.26?
We use mstflint together with a mainline kernel 6.5 at the moment.
thillux
commented
8 months ago Update: with kernel 6.6 and a more recent rdma-core version we were able to trigger a reset succesfully from BF2. But ran into the 60s timeout. dmesg showed, that the reset worked.
ogalbxela
commented
2 months ago Had a conversation with the owner from our side. Direction was: please use mstflint-4.28 (just released) and the latest available driver to flash the latest published firmware. Please also query the device with "mstfwreset" (mstfwreset -d DEVICE q). It will list "sync"-capabilities for you.
Something like:
mstfwreset -d 81:00.0 q
<some output omitted>
Reset-sync (relevant only for reset-level 3):
0: Tool is the owner -Not supported
1: Driver is the owner -Supported (default)For "sync 0" - tool is the owner of reset flow and reset command should be issued from both host and arm side For "sync 1" - driver is the owner
Using mstflint compiled from source code:
On a Bluefield-2 w/ BMC
I am trying to update the fw to the latest version. After running mstflint -d -i <.bin> burn, this is the state of the bluefield
mstfwreset fails with the following error:
If I disable sync and run this again, it hangs on waiting for other hosts, and times out
I can skip the fsm sync but this results in the fw reset failing without a particular error message
Note that I tried rebooting the host machine at this point, however the fw update has not been applied after reboot.
The only way I have found to apply the updated firmware is to switch the device to "NIC mode", after which fwreset is able to successfully apply the pending configurations, as well as switch to the updated fw version.