mirror of
https://github.com/opnsense/src.git
synced 2026-06-17 12:41:39 -04:00
20e15e905c
When encountering a failed NIC, the mlx5 driver will wait up to 120 secs for the firmware to respond. This timeout is absurdly huge, and leads to boot times of 40 minutes to over an hour on our servers when a NIC fails. This is because the driver will attempt to attach to the failed NIC multiple times (once for each driver loaded after mlx5), and wait 2 minutes on each attempt. This happens because the mlx5 driver is still the best match for the device. This delay then triggers watchdog timeouts in our environment, rendering servers with a failed NIC entirely unbootable without manual intervention. Note that FW_INIT_WARN_MESSAGE_INTERVAL must also be decreased, as it must be less than the init timeout. Reviewed by: kib (initial version, before reducing warn interval) Sponsored by: Netflix |
||
|---|---|---|
| .. | ||
| mlx5_accel | ||
| mlx5_core | ||
| mlx5_en | ||
| mlx5_fpga | ||
| mlx5_fpga_tools | ||
| mlx5_ib | ||
| mlx5_lib | ||
| cmd.h | ||
| cq.h | ||
| crypto.h | ||
| device.h | ||
| diagnostics.h | ||
| doorbell.h | ||
| driver.h | ||
| fs.h | ||
| mlx5_ifc.h | ||
| mlx5_rdma_if.h | ||
| mlx5io.h | ||
| mpfs.h | ||
| port.h | ||
| qp.h | ||
| srq.h | ||
| tls.h | ||
| vport.h | ||