[lm-sensors] problems loading i2c-proc

[lm-sensors] problems loading i2c-proc

[Steven Timm]

System configuration:
Kernel 2.4.21-32.0.1.ELsmp as downloaded from RHEL vs 3 update 5
I2C 2.9.1

Problems happen in i686 and athlon architectures.  Opteron (x86_64)is ok.
Compiles are clean on all.
When I do  modprobe i2c-proc, the following happens:

/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol create_proc_entry_R0be93f3a
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol kmalloc_R93d4cfe6
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol __generic_copy_to_user_Rd523fdd3
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol remove_proc_entry_Re94539f7
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol proc_bus_Rd6eafc0f
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol sprintf_R1d26aa98
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol kfree_R037a0cba
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: unresolved 
symbol printk_R1b7d4074
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod 
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o failed
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod 
i2c-procfailed


Any idea what might be wrong?  Some wrong header getting into the compile
somewhere?  Other?  As I say, x86_64 version is OK.

Steve Timm




-- 
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team

[lm-sensors] problems loading i2c-proc

[Jean Delvare]

Hi Steven,

> Problems happen in i686 and athlon architectures.  Opteron (x86_64)is
> ok. Compiles are clean on all.
> When I do  modprobe i2c-proc, the following happens:
> 
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol create_proc_entry_R0be93f3a
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol kmalloc_R93d4cfe6
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol __generic_copy_to_user_Rd523fdd3
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol remove_proc_entry_Re94539f7
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol proc_bus_Rd6eafc0f
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol sprintf_R1d26aa98
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol kfree_R037a0cba
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
> unresolved  symbol printk_R1b7d4074
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
> 
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o failed
> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
> 
> i2c-procfailed
> 
> 
> Any idea what might be wrong?  Some wrong header getting into the
> compile somewhere?  Other?  As I say, x86_64 version is OK.

Make sure you have File Systems > /proc file system support enabled
(CONFIG_PROC_FS). In theory i2c-proc should depend on it (in Config.in),
but now it looks like it doesn't...

Another possibility is a problem with symbol versioning, which you seem
to have enabled. It should work, but maybe you could try without
versioning, just in case.

Hope that helps,
-- 
Jean Delvare

[lm-sensors] problems loading i2c-proc

[Steven Timm]

On Thu, 7 Jul 2005, Jean Delvare wrote:

> Hi Steven,
>
>> Problems happen in i686 and athlon architectures.  Opteron (x86_64)is
>> ok. Compiles are clean on all.
>> When I do  modprobe i2c-proc, the following happens:
>>
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol create_proc_entry_R0be93f3a
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol kmalloc_R93d4cfe6
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol __generic_copy_to_user_Rd523fdd3
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol remove_proc_entry_Re94539f7
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol proc_bus_Rd6eafc0f
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol sprintf_R1d26aa98
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol kfree_R037a0cba
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol printk_R1b7d4074
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
>>
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o failed
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
>>
>> i2c-procfailed
>>
>>
>> Any idea what might be wrong?  Some wrong header getting into the
>> compile somewhere?  Other?  As I say, x86_64 version is OK.
>
> Make sure you have File Systems > /proc file system support enabled
> (CONFIG_PROC_FS). In theory i2c-proc should depend on it (in Config.in),
> but now it looks like it doesn't...

It's enabled.
>
> Another possibility is a problem with symbol versioning, which you seem
> to have enabled. It should work, but maybe you could try without
> versioning, just in case.

I have no idea either how to enable or disable symbol versioning.  Have
never had to do anything about this before in previous i2c releases
compiled on the same machines.

steve

>
> Hope that helps,
>

-- 
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team

[lm-sensors] problems loading i2c-proc

[Jean Delvare]

Hi Steven,

> > Another possibility is a problem with symbol versioning, which you
> > seem to have enabled. It should work, but maybe you could try
> > without versioning, just in case.
> 
> I have no idea either how to enable or disable symbol versioning. 
> Have never had to do anything about this before in previous i2c
> releases compiled on the same machines.

This is enabled at kernel compilation time in Loadable module support >
Set version information on all module symbols.

You didn't tell us how you are installing i2c. Have you patched your
kernel sources tree? Or are you compiling i2c separately? In the latter
case, is the kernel a stock one or did you recompile it at some point?

Can you share your kernel configuration file so that I try reproducing
the problem?

Thanks,
-- 
Jean Delvare

[lm-sensors] problems loading i2c-proc

[Steven Timm]

On Fri, 8 Jul 2005, Jean Delvare wrote:

> Hi Steven,
>
>>> Another possibility is a problem with symbol versioning, which you
>>> seem to have enabled. It should work, but maybe you could try
>>> without versioning, just in case.
>>
>> I have no idea either how to enable or disable symbol versioning.
>> Have never had to do anything about this before in previous i2c
>> releases compiled on the same machines.
>
> This is enabled at kernel compilation time in Loadable module support >
> Set version information on all module symbols.
>
> You didn't tell us how you are installing i2c. Have you patched your
> kernel sources tree? Or are you compiling i2c separately? In the latter
> case, is the kernel a stock one or did you recompile it at some point?
>
My process
1) take the kernel-source rpm as it comes from RedHat
2) recompile it as it is
3) compile the i2c sources separately, but pointed at the
kernel configs and includes in that kernel tree.

> Can you share your kernel configuration file so that I try reproducing
> the problem?

Kernel config is just the one that would be in
red hat 2.4.21-32.0.1.ELsmp.  I haven't changed anything.
Can send by separate E-mail if you want.

Steve Timm


>
> Thanks,
>

-- 
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team

[lm-sensors] problems loading i2c-proc

[Steven Timm]

It appears that this problem was due to my mistakely compiling
the modules for a SMP kernel with a uniprocessor kernel config.
Have fixed that, and things load OK now.

Steve Timm


On Thu, 7 Jul 2005, Jean Delvare wrote:

> Hi Steven,
>
>> Problems happen in i686 and athlon architectures.  Opteron (x86_64)is
>> ok. Compiles are clean on all.
>> When I do  modprobe i2c-proc, the following happens:
>>
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol create_proc_entry_R0be93f3a
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol kmalloc_R93d4cfe6
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol __generic_copy_to_user_Rd523fdd3
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol remove_proc_entry_Re94539f7
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol proc_bus_Rd6eafc0f
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol sprintf_R1d26aa98
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol kfree_R037a0cba
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol printk_R1b7d4074
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
>>
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o failed
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
>>
>> i2c-procfailed
>>
>>
>> Any idea what might be wrong?  Some wrong header getting into the
>> compile somewhere?  Other?  As I say, x86_64 version is OK.
>
> Make sure you have File Systems > /proc file system support enabled
> (CONFIG_PROC_FS). In theory i2c-proc should depend on it (in Config.in),
> but now it looks like it doesn't...
>
> Another possibility is a problem with symbol versioning, which you seem
> to have enabled. It should work, but maybe you could try without
> versioning, just in case.
>
> Hope that helps,
>

-- 
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team

[lm-sensors] problems loading i2c-proc

[Jean Delvare]

Hi Steven,

> It appears that this problem was due to my mistakely compiling
> the modules for a SMP kernel with a uniprocessor kernel config.
> Have fixed that, and things load OK now.

Oh, great. This explains why I was unable to reproduce the problem, no
matter the kernel version nor how hard I tried.

Anyway, glad you finally figured it out. I'll try to remember in case
others report the same problem. It was really not obvious what the
problem was from the logs alone.

--
Jean Delvare