mstfwreset fails when card is in DPU mode #830
Comments
|
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. |
|
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. |
|
Had a conversation with the owner from our side. 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 |
|
Hi @ogalbxela , Even we faced the same error of "Synchronization by driver is not supported in the current state of this device." during mstfwreset. As suggested in the thread above we updated the Firmware to latest (24.42.1000) and also took v4.29 mstflint latest. But still we are facing issue during mstfwreset. (Even with v4.28 it gives the same error as in v4.29) ~]$ sudo mstflint --version ~]$ sudo mstfwreset -d 17:00.0 q Reset-levels: Reset-types (relevant only for reset-levels 1,3,4): Reset-sync (relevant only for reset-level 3): Reset-reason: Warm reset Note that the Reset-sync (sync 1) shows supported. But still it is not working. The reset level for device, 0000:17:00.0 is: 3: Driver restart and PCI reset |
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.
The text was updated successfully, but these errors were encountered: