Tom,
REGPARM indicates a gcc function calling convention.
A couple of things you can try now
- After recompilation, I suppose you have rebooted into your new kernel?
- It still looks like pvfs2 is not being built against the right
kernel sources and
possibly by a different compiler that was used to build the kernel..
- rebuild the kernel and turn off the CONFIG_REGPARM option.. Don't
know where it appears.. You could just edit the .config file in
/usr/src/linux and turn it off.. After rebuild, reboot and rebuild
pvfs2 and reload.
- Edit /usr/src/linux/include/linux/autoconf.h and add a
#define CONFIG_REGPARM 1, and rebuild pvfs2..
(OR)
As a quick short term hack, you could do the following. It is a sad
hack and should do the trick...
Open /usr/src/linux/include/linux/vermagic.h and add the following.
Actually, can you paste the line containing VERMAGIC_STRING from this file?
#ifdef CONFIG_REGPARM
#define MODULE_REGPARM_VERMAGIC "REGPARM "
#else
#define MODULE_REGPARM_VERMAGIC ""
#endif
#define VERMAGIC_STRING \
UTS_RELEASE " " \
MODULE_VERMAGIC_SMP MODULE_VERMAGIC_PREEMPT \
MODULE_VERMAGIC_MODULE_UNLOAD MODULE_ARCH_VERMAGIC
\
MODULE_REGPARM_VERMAGIC <-- add this last part
thanks,
Murali
On 5/30/07, Tommy Butler <[EMAIL PROTECTED]> wrote:
I started with a fresh build tree of pvfs2. I deleted the old directory,
created a new build tree by extracting from the source. I then patched the
tree. I then went into /usr/src/linux and ran a `make modules` in order to
generate the Module.symvers file that was missing per the previous error. I
then went back to the /usr/src/pvfs2 build tree and ran a configure against
the new kernel source tree (`./configure -with-mpi=/usr/bin/mpirun
-with-kernel=/usr/src/linux`)
I then did `make && make install && make kmod_install` and that went well
without any errors. Then...
once again:
[EMAIL PROTECTED]:/usr/src/pvfs2# insmod src/kernel/linux-2.6/pvfs2.ko
insmod: error inserting 'src/kernel/linux- 2.6/pvfs2.ko': -1 Invalid module
format
[EMAIL PROTECTED]:/usr/src/pvfs2# dmesg|tail -n1
pvfs2: version magic '2.6.18 mod_unload 486 gcc-4.1' should be '2.6.18-4-486
mod_unload 486 REGPARM gcc-4.1'
I have no idea what "REGPARM" is supposed to signify, but it seems to be
the clue I need to figure out the rest of the problem. Please, any
thoughts?
*sigh* =(
--
Tommy Butler
On 5/31/07, Murali Vilayannur <[EMAIL PROTECTED]> wrote:
> Tom,
> DId you rerun configure on PVFS2 with
> --with-kernel=/path/to/newest/kernel sources?
> It is best if you make clean prior to rerunning configure?
> Sorry that it is taking you longer than it takes normally..
> Please let us know how/what is going wrong and I am sure we can figure
this out
> and get you going soon.
> It is a case of wrong build tool version/kernel sources.
> thanks,
> Murali
>
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
