[openib-general] Re: Loading kdapl on 2.6.11.6

James Lentini jlentini at netapp.com
Mon Sep 26 10:27:21 PDT 2005



On Mon, 26 Sep 2005, Hal Rosenstock wrote:

> On Mon, 2005-09-26 at 13:13, James Lentini wrote:
> > On Mon, 26 Sep 2005, Hal Rosenstock wrote:
> > 
> > > Hi James,
> > > 
> > > When loading kdapl built on 2.6.11.6, I keep getting the following:
> > > 
> > > kdapl_/sbin/modprobe kdapl_ib
> > > FATAL: Error inserting kdapl_ib
> > > (/lib/modules/2.6.11.6/kernel/drivers/infiniband/ulp/kdapl/ib/kdapl_ib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
> > > ib: disagrees about version of symbol dat_registry_remove_provider
> > > kdapl_ib: Unknown symbol dat_registry_remove_provider
> > > kdapl_ib: disagrees about version of symbol dat_registry_add_provider
> > > kdapl_ib: Unknown symbol dat_registry_add_provider
> > > kdapl_ib: disagrees about version of symbol dat_registry_remove_provider
> > > kdapl_ib: Unknown symbol dat_registry_remove_provider
> > > kdapl_ib: disagrees about version of symbol dat_registry_add_provider
> > > kdapl_ib: Unknown symbol dat_registry_add_provider
> > > kdapl_ib: disagrees about version of symbol dat_registry_remove_provider
> > > kdapl_ib: Unknown symbol dat_registry_remove_provider
> > > kdapl_ib: disagrees about version of symbol dat_registry_add_provider
> > > kdapl_ib: Unknown symbol dat_registry_add_provider
> > > 
> > > I've rebuilt the kdapl, kdapl_ib, and dat modules and rebooted but this
> > > still occurs. Any idea what's wrong ? Thanks.
> > 
> > What is the lsmod output before you modprobe kdapl_ib?
> 
> [root at localhost hal]# /sbin/modprobe kdapl
> [root at localhost hal]# /sbin/modprobe kdapl_ib
> FATAL: Error inserting kdapl_ib (/lib/modules/2.6.11.6/kernel/drivers/infiniband/ulp/kdapl/ib/kdapl_ib.ko): Unknown symbol in module, or unknown parameter (see dmesg)
> 
> > If there is an 
> > old module being autmatically loaded that defines 
> > dat_registry_remove_provider, etc. this would be the type of error I 
> > would expect.
> 
> What are the potential old modules other than dat, kdapl, and kdapl_ib
> here ? dat must somehow be old (or newer)...

The dat module is the problem. When we moved the code to the trunk, we 
called the dat registry module kdapl. There shouldn't be a "dat" 
module. 

If you rmmod dat, I expect that this will fix your problem.

james



More information about the general mailing list