ocrdma module may show kernel as tainted
Environment
- Red Hat Enterprise Linux 7
Issue
- Previously, loading the ocrdma module for Emulex OneConnect cards at boot time, including those that do not support Remote Direct Memory Access (RDMA), caused the kernel to be tainted with the Technology Preview status. With this update, the module is not loaded automatically, which fixes the problem. To re-enable automatic loading of Technology Preview modules for RDMA support on capable hardware, the user can edit the /etc/rdma/rdma.conf configuration file for the RDMA infrastructure
Resolution
- RHEL7.0-7.3: Install updated RDMA package from 2017:1299
- RHEL7.4 and later: Ensure that the
ocrdmamodule does not get loaded, with kbase: How do I blacklist a kernel module to prevent it from loading automatically?
Note: Once the ocrdma module is loaded, it might interact with other modules, like the be2net module. So on systems where lsmod indicates that be2net is relying on ocrdma, unloading of ocrdma can lead to issues like the be2net-provided network interfaces going down. On such systems, the system should get a service downtime (where it's ok that the network interfaces go down), the admin should login via console, and then perform the blacklisting procedure.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments