RE: Unresolved Symbol in Module

[Paul Gearon <pag@PISoftware.com>]

On Thu, 8 Mar 2001, Narayana, Venkat A. wrote:

> Thanks for pointing me to docs.I shall read them.

Yeah, I have to read a lot more of them too.  ;-)

> However, i noticed that when i build my module without
> CONFIG_MODVERSION, then this is my 'nm' output:
> 	hello.o:         U init_task_union
> 	hello.o:         U printk
>
> whereas, 'cat /proc/ksyms | grep printk' gives me
> c011331c printk_R1b7d4074.
>
> I am not sure from where my module is pickingup 'printk'?
> Also, when i build module with CONFIG_MODVERSION ON, then
> 'nm' output gave me:
> 	hello.o:         U printk_Rsmp_1b7d4074
>
> In the first case, i can load my module but in second case i can't.
>  Help!what's the difference.


I'm not sure why you can install a module with "printk" into a kernel with
"printk_R1b7d4074".  insmod must be acting intelligently here.  I'm still
learning this stuff myself  :-)

However, your second module is being built with the CONFIG_SMP flag on.
You DON'T want to do this, unless you are running on an SMP system.
Since your kernel symbols aren't SMP, then you can't insert an SMP module.

Regards,
Paul Gearon
pag@PISoftware.com

Catapultam habeo. Nisi pecuniam omnem mihi dabis, ad caput tuum saxum
immane mittam.
(Translation from latin: "I have a catapult. Give me all the money,
or I will fling an enormous rock at your head.")


-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.surriel.com/kernelnewbies.shtml