During ISSU, "mlxsw_minimal" driver still trying to access firmware, in some cases FW could return some wrong critical threshold value which will cause switch shutdown. **- How I did it** In order to prevent "mlxsw_minimal" driver from accessing ASIC during ISSU, SDK will raise "OFFLINE" 'udev' event at the early beginning of such flow. When this event is received, hw-management will remove "mlxsw_minimal" driver. There is no need to implement the opposite "ONLINE" event since this flow is ended up with "kexec". **- How to verify it** repeatedly perform warm reboot, make sure there is no switch shutdown occurred. |
||
---|---|---|
.. | ||
docker-saiserver-mlnx | ||
docker-syncd-mlnx | ||
docker-syncd-mlnx-rpc | ||
hw-management | ||
issu-version | ||
mft | ||
mlnx-platform-api | ||
mlnx-sai | ||
sdk-src | ||
.gitignore | ||
asic_table.j2 | ||
docker-ptf-mlnx.dep | ||
docker-ptf-mlnx.mk | ||
docker-saiserver-mlnx.dep | ||
docker-saiserver-mlnx.mk | ||
docker-syncd-mlnx-rpc.dep | ||
docker-syncd-mlnx-rpc.mk | ||
docker-syncd-mlnx.dep | ||
docker-syncd-mlnx.mk | ||
fw.dep | ||
fw.mk | ||
hw-management.dep | ||
hw-management.mk | ||
issu-version.dep | ||
issu-version.mk | ||
libsaithrift-dev.dep | ||
libsaithrift-dev.mk | ||
mft.dep | ||
mft.mk | ||
mlnx-ffb.dep | ||
mlnx-ffb.mk | ||
mlnx-ffb.sh | ||
mlnx-fw-upgrade.j2 | ||
mlnx-onie-fw-update.dep | ||
mlnx-onie-fw-update.mk | ||
mlnx-onie-fw-update.sh | ||
mlnx-platform-api.dep | ||
mlnx-platform-api.mk | ||
mlnx-sai.dep | ||
mlnx-sai.mk | ||
mlnx-ssd-fw-update.dep | ||
mlnx-ssd-fw-update.mk | ||
mlnx-ssd-fw-update.sh | ||
one-image.dep | ||
one-image.mk | ||
peripheral_table.j2 | ||
platform.conf | ||
rules.dep | ||
rules.mk | ||
sdk.dep | ||
sdk.mk |