Re: [HPDD-discuss] Module version is incorrect

By the way, I found JIRA site only after I posted to HPDD forum, so I have opened the case there too, cause I didn't found anything similar. May be we need to move discussion there or somehow to connect them. The case is LU-5597

I understand that, but the OFED does generate Module.symvers file in its directory after kernel drivers were compiled. So, there are two files, one from OS under /usr/src/linux-3.13-XXX and another under /usr/src/mlnx-ofed-kernel-2.3. During Luster 'configure' stage there is a message that external Module.symvers file (from OFED installation) was found and it was copied to Lustre source folder. This file has correct versions that points to OFED drivers. So, I can't understand why Lustre compilation still using OS provided kernel Module.symvers file at 'modpost' phase. If workaround is to replace version in /usr/src/linux-3.13-XXXX/ file than it will works only until the OFED is uninstalled. The bottom line, I'm still thinking where is the bug: Is it kernel makefile Is it OFED Is it Lustre that doesn't use correct file Another question, Is the same failure happens on community OFED? I wasn't able to install OFED-3.12 because of kernel modules compilation failed. Probably missing backports, but I didn't go deep in the investigation. Does anybody know the answer? On Thu, Sep 11, 2014 at 12:21 PM, Simmons, James A. <simmonsja(a)ornl.gov&gt; wrote: >>After installing Mellanox MOFED, I configured Luster in the following way >>./configure --disable-server --with-o2ib=/usr/src/mlnx-ofed-kernel-2.3 >>and was able to compile kernel modules. >>But the version of function symbols that were compiled in ko2iblnd >>module belongs to original kernel modules and not to the OFED >>modules. As results compiled module refuse to load. > > This happens so often we really should post this on a FAQ. You need to > replace all the default module symbols in your Module.symvers with > the ones generated by the MLNX stack.