[Myrinet] unresolved symbol loading gm-1.5.2.1 on Alpha

Nathan Dauchy <[email protected]>
Newsgroups gmane.network.myrinet.general
Organization High Performance Technologies, inc.
Message-ID <[email protected]>
Greetings,

I am trying to upgrade gm to 1.5.2.1 on an Alpha cluster running 
linux-2.4.18 and get the following error when loading the GM module:

[[email protected] gm]# /sbin/insmod sbin/gm
sbin/gm: unresolved symbol __load_new_mm_context

As suggested in Myricom's FAQ, 
(http://www.myri.com/scs/faq/faq-install.html#install7b)
I have recompiled the kernel to make sure that the source that GM is
compiled against is exactly the same as the running kernel.

[[email protected] gm]# uname -a
Linux node.n-1.t-0 2.4.18 #5 Wed Sep 4 09:07:40 MDT 2002 alpha unknown

This kernel is compiled with CONFIG_MODVERSIONS not defined, when I
tried with it, I get many more (~50) "unresolved symbol" errors.

Has anyone else seen a similar problem?  Or perhaps gotten 
gm-1.5.2.1/linux-2.4.18/Alpha working successfully?


Some additional information:
- Previously, this cluster was running gm-1.4, which worked fine, but we
would like to take advantage of recent enhancements and bug fixes.
- I have also tried the linux-2.4.19 kernel, which allegedly
incorporates several patches for Alpha, and still get the same error.
- I downloaded gm-1.5.1_Linux and it does NOT have the same
"unresolved symbol" error that gm-1.5.2.1 does with the linux-2.4.18
kernel.  gm-1.5.2_Linux DOES report the same error, so I am thinking it 
might be that a bug was introduced somewhere in the changes from
1.5.1 to 1.5.2.
- This is a diskless cluster, so 1) I am building on a different node 
than I am running on, but it is still an Alpha, and this worked fine for 
gm-1.4.  and 2) The kernel is fairly stripped down, so perhaps there is 
an option that most sites have that I am missing.  Successfull 2.4.18 
.config files might be helpful.


All suggestions appreciated!

Thanks,
Nathan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.