This technical advisory addresses the issue where due to a change to a RHEL 8.4 kernel abi package name in the install script for OPXS 10.11.1.0 (RHEL 8.4) the installation process may be prevented from completing.
This technical advisory addresses the issue where due to prior, unofficial use of the PCI ID recently assigned to Cornelis Networks, the value “Cast Navigation LLC” may appear in the subvendor field of the lspci command for a Cornelis HFI adapter.
This technical advisory addresses the issue where Omni-Path Host Fabric Interface Adapters installed in platforms supporting PCIe Gen 4 do not train to PCIe Gen 3 speeds during boot over fabric using Omni-Path UEFI Firmware.
This technical advisory addresses the issue where with irqbalance running, hfi1 driver interrupt mappings are being remapped during operation to a non-optimal state. This issue could occur at any time following the initial boot.
This technical advisory addresses the issue where because atomic_fetch_add_unless() was added to the Kernel API in 4.18.0-193.28.1, the OPA IFS 10.10.3.x driver cannot be compiled or installed. Note: This issue affects RHEL 8.2 and its equivalent CentOS-8 (2004).
This technical advisory addresses the issue where the NVIDIA Collectives Communications Library (NCCL) does not come with an optimized transport for Omni-Path. Use of the Verbs transport does not take maximum advantage of the Omni-Path HFI ASIC and GPUDirect support that is available with Omni-Path Architecture PSM2 and hfi1.
This technical advisory addresses the issue where the hfi1 driver enables a character device that users open through normal file system methods. When the file is opened, a pointer to the current->memory management (mm) is saved in the private data for the file handle. This is then used for input/output control (IOCTL) and write_iter() commands from the user for pinning and unpinning of memory on behalf of the user. The saved value is remembered in an attempt to handle the case where the context (current) value that calls the close on the file—such as being killed by a signal or Out Of Memory (OOM) killer—is different than the original user.