The following is a list of the known bugs in this FreeBSD version and in earlier versions.
|
Internal Reference Number |
Bug Details |
|
2684280 |
Description: VXLAN is not supported when SR-IOV is enabled. |
| Workaround: N/A | |
| Keywords: VXLAN, SR-IOV | |
| Discovered in Release: 3.7.0 | |
|
2703601 |
Description: The following harmless warning messages might be seen when running RDMA apps and can be safely ignored: _ib_modify_qp rq_psn overflow, masking to 24 bits |
| Workaround: N/A | |
| Keywords: RDMA, warning messages | |
| Discovered in Release: 3.7.0 | |
|
2685136 |
Description: VXLAN stateless offload is not enabled for VLAN interfaces. |
| Workaround: N/A | |
| Keywords: VXLAN | |
| Discovered in Release: 3.7.0 | |
|
2703601 |
Description: ping6 stops after toggling the standby interface for the second time. |
| Workaround: N/A | |
| Keywords: IPv6, toggling | |
| Discovered in Release: 3.6.0 | |
|
2393686 |
Description: The LAG interface loses IPv4 address after deleting one of its standby interface (active/not active). |
| Workaround: N/A | |
| Keywords: LAG, IPv4 | |
| Discovered in Release: 3.6.0 | |
|
2337410 |
Description: Packet pacing hardware offload scaling is limited to ~30K connections over ConnectX-4 due to cache limitations. |
| Workaround: N/A | |
| Keywords: Packet pacing; hardware offload; cache | |
| Discovered in Release: 3.6.0 | |
|
2389793 |
Description: mlx5 driver supports creating up to 127 VFs in the host. Nevertheless, the number of VFs that can be created is limited by some system resources, such as the number of BARs layout in the address space, the number of configured IRQs in the kernel, the position of the PF and VF in the PCIe config address space for sibling ports, and others. |
| Workaround: N/A | |
| Keywords: SR-IOV; VF | |
| Discovered in Release: 3.6.0 | |
|
- |
Description: When reloading the module during heavy traffic, FreeBSD driver may become unstable. |
| Workaround: N/A | |
| Keywords: Reload, stress, heavy traffic | |
| Discovered in Release: 3.5.2 | |
|
1578093 |
Description: ibstat tool shows the wrong value of “rate” after unplugging the cable from the HCA. |
| Workaround: N/A | |
| Keywords: ibstate, rate | |
| Discovered in Release: 3.5.0 | |
|
1439351 |
Description: Link local GIDs are dysfunctional when IPv6 address is configured for the first time. |
|
Workaround: Set the net device state to “up”. For example: # ifconfig mce0 up |
|
| Keywords: RoCE, IPv6 | |
| Discovered in Release: 3.4.2 | |
|
1435021 |
Description: All Rx priority pause counters values increase when Rx global pause is enabled. |
| Workaround: Ignore Rx priority pause counters when Rx global pause is enabled. | |
| Keywords: Rx pause counters, priority | |
| Discovered in Release: 3.4.2 | |
|
1434034 |
Description: RDMA-CM applications do not work when PCP is configured on one side of the connection. |
| Workaround: Make sure PCP is configured on both sides of the connection. | |
| Keywords: RDMA-CM, PCP | |
| Discovered in Release: 3.4.2 | |
|
1313461 |
Description: When Packet Pacing is enabled in firmware, only one traffic class will be supported by the firmware. |
|
Workaround: Disable Packet Pacing in the firmware configuration. For example:
# cat /tmp/disable_pp.txt MLNX_RAW_TLV_FILE 0x00000004 0x0000010c 0x00000000 0x00000000 # mlxconfig -d pci0:4:0:0 -f /tmp/disable_pp.txt set_raw |
|
| Keywords: Firmware, Packet Pacing | |
| Discovered in Release: 3.4.2 | |
|
1227471 |
Description: When loading and unloading linuxkpi module, the following error message will appear in the dmesg, indicating that a memory leak has occurred:
“Warning: memory type linux leaked memory on destroy (2 allocations, 64 bytes leaked). Warning: memory type linuxcurrent leaked memory on destroy (7 allocations, 896 bytes leaked).” |
| Workaround: N/A | |
| Keywords: linuxkpi | |
| Discovered in Release: 3.4.1 |