Mallory, Rob wrote:
I sat with our linux guy a bit and we plugged around, and found no
mixup of kernel-headers or compile environment. (that we could tell)
modprobe lnet works, and so do the others (listed in the original strace), but we found
that ptlrpc.ko is getting invalid argument.
from dmesg:
[1196856.351524] ptlrpc: disagrees about version of symbol class_export_put
This indicates you have mismatched ksyms at link, and are probably
linking against the wrong kernel modules.
Does this give more clues? Has anyone else run on a sles trace
kernel?
I think my trace packages work, but I have convoluted way of building
Lustre from a heavily modified spec in an rpmbuild based system.
The lustre autoconf and rpm scripts are clueless about non-default
kernel flavors. You need to specify everything kernel related to
prevent it from using default flavor bits. This is the relevant part of
how I do it from an rpm spec
%if %is_sles11
%define setup_flavor() \
krequires=$( echo $kversion | sed -e s/-%1// ); \
ksource=/usr/src/linux-$krequires; \
kobjdir=/usr/src/linux-obj/%_target_cpu/%1; \
kconfig=$kobjdir/.config; \
%eval_configure --with-linux=$ksource \
--with-linux-obj=$kobjdir \
--with-linux-config=$kconfig \
Make sure you have kernel-trace kernel-trace-base kernel-trace-devel and
kernel-source installed.
Hope that helps!