You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MEI warnings were observed in dmesg when out of tree i915 driver is loaded on RHEL 9.2 based OCP 4.13.10. Note, MEI is the original name of the driver. The out of tree driver equivalent is called CSE. Refer to dmesg output below. The goal of this issue is to understand if these warnings are expected, what is the meaning behind the warnings, and what is the root cause and potential solution.
Theory:
This behavior may be expected as we are not unloading the in-tree CSE (aka MEI) driver. As a result, the out of tree MEI driver is never loaded and thus the in-tree MEI is potentially trying to use out of tree FW to initialize. This is an incompatibility.
Solution:
Potential solution is to unload in-tree MEI and see if the out of tree MEI loads successfully and this error goes away. This solution needs to be tested. This is another potential use case for KMM to unload more than one in-tree driver.
Summary:
MEI warnings were observed in dmesg when out of tree i915 driver is loaded on RHEL 9.2 based OCP 4.13.10. Note, MEI is the original name of the driver. The out of tree driver equivalent is called CSE. Refer to dmesg output below. The goal of this issue is to understand if these warnings are expected, what is the meaning behind the warnings, and what is the root cause and potential solution.
Theory:
This behavior may be expected as we are not unloading the in-tree CSE (aka MEI) driver. As a result, the out of tree MEI driver is never loaded and thus the in-tree MEI is potentially trying to use out of tree FW to initialize. This is an incompatibility.
Solution:
Potential solution is to unload in-tree MEI and see if the out of tree MEI loads successfully and this error goes away. This solution needs to be tested. This is another potential use case for KMM to unload more than one in-tree driver.
### dmesg output: