Insmod messages and modules space

Insmod messages and modules space

[Shay Deloya]

Hi All,

1.Should text segment of module after insmod be in KSEG2 or KUSEG ? 
I've notices that the module address after insmod are c0... instead of 80...
Is it insmod Bug  ?
2. I keep getting in insmod of busybox pkg , "relocation overflow" message 
especially on printk symbols , when I debug the code, changing some function 
declaration from static int func () to int func()  , makes the module to 
insert correctly , anyone ?

Thanks,
-- 
Shay Deloya
______________________________________
Software Developer
Jungo - R&D
email: shayd@jungo.com
web: http://www.jungo.com
Phone: 1-877-514-0537(USA)  +972-9-8859365(Worldwide) ext. 221
Fax:   1-877-514-0538(USA)  +972-9-8859366(Worldwide)

Re: Insmod messages and modules space

[Ralf Baechle]

On Mon, Apr 09, 2001 at 08:10:16PM +0200, Shay Deloya wrote:

> 1.Should text segment of module after insmod be in KSEG2 or KUSEG ? 
> I've notices that the module address after insmod are c0... instead of 80...
> Is it insmod Bug  ?

It's a sign of insmod working properly :)

> 2. I keep getting in insmod of busybox pkg , "relocation overflow" message 
> especially on printk symbols , when I debug the code, changing some function 
> declaration from static int func () to int func()  , makes the module to 
> insert correctly , anyone ?

Two possibilities, either you're using a too old and broken version of
modutils or you used inapropriate options to compile your module.

  Ralf

Re: Insmod messages and modules space

[Ian Soanes]

Ralf Baechle wrote:
> 
> On Mon, Apr 09, 2001 at 08:10:16PM +0200, Shay Deloya wrote:
> 
> > 1.Should text segment of module after insmod be in KSEG2 or KUSEG ?
> > I've notices that the module address after insmod are c0... instead of 80...
> > Is it insmod Bug  ?
> 
> It's a sign of insmod working properly :)
> 
> > 2. I keep getting in insmod of busybox pkg , "relocation overflow" message
> > especially on printk symbols , when I debug the code, changing some function
> > declaration from static int func () to int func()  , makes the module to
> > insert correctly , anyone ?
> 
> Two possibilities, either you're using a too old and broken version of
> modutils or you used inapropriate options to compile your module.
> 

Compiling with -mlong-calls worked for me when I had the same problem
(modutils 2.4.5). Relinking the module with 'ld -r -o new_mod.o
orig_mod.o' was useful too ...it worked around some 'exceeds
local_symtab_size' messages.

Ian

Re: Insmod messages and modules space

[Keith Owens]

On Tue, 10 Apr 2001 09:55:16 +0100, 
Ian Soanes <ians@lineo.com> wrote:
>> On Mon, Apr 09, 2001 at 08:10:16PM +0200, Shay Deloya wrote:
>> > 2. I keep getting in insmod of busybox pkg , "relocation overflow" message
>> > especially on printk symbols
>
>Compiling with -mlong-calls worked for me when I had the same problem
>(modutils 2.4.5).

Compiling what with -mlong-calls, modutils or the kernel modules?  I
guess it must be the modules, in which case adding
  MODFLAGS += -mlong-calls
in arch/$(ARCH)/Makefile is the best fix.

Re: Insmod messages and modules space

[Ian Soanes]

Keith Owens wrote:
> 
> On Tue, 10 Apr 2001 09:55:16 +0100,
> Ian Soanes <ians@lineo.com> wrote:
> >> On Mon, Apr 09, 2001 at 08:10:16PM +0200, Shay Deloya wrote:
> >> > 2. I keep getting in insmod of busybox pkg , "relocation overflow" message
> >> > especially on printk symbols
> >
> >Compiling with -mlong-calls worked for me when I had the same problem
> >(modutils 2.4.5).
> 
> Compiling what with -mlong-calls, modutils or the kernel modules?  I
> guess it must be the modules, in which case adding
>   MODFLAGS += -mlong-calls
> in arch/$(ARCH)/Makefile is the best fix.

Yes... the modules.