Symptoms

Component fpgamgr experiences segmentation fault after failed FPGA firmware update and persists in a reboot loop. The CLI command "show cluster nodes node state platform fpga-state" indicates that FPGA_STATE persists in FPGA_INIT and never reaches the state FPGA_RDY.

Impact

A failure in the FPGA firmware update process results in one or more FPGA devices not being detected on the PCI bus. This, in turn, causes a segmentation fault in the FPGA SDK upon the startup of the fpgamgr component, leading to a continuous reboot cycle until the FPGA issue is resolved.

Conditions

FPGA firmware update fails and one or more of the FPGA devices does not show up on the PCI bus. This causes a FPGA SDK segmentation fault upon the fpgamgr component startup, and perpetual reboot loop so long as the FPGA issue persists.

Workaround

None. Perpetual reboot loops after trying to load FPGA firmware that do not recover typically indicates a hardware error and requires an RMA.

Fix Information

One of the BARs fails to initialize when the PCIE speed does not load at the intended Generation. This issue was causing a segmentation fault in the SDK, but it has now been resolved by having the SDK notify the fpgamgr of the missing BAR instead. While the device may still fail to load, the fpgamgr will no longer experience a crashing loop as a result.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips