insmod failure: "Unhandled relocation" errors

insmod failure: "Unhandled relocation" errors

[Gilad Benjamini]

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

Hi,
I've built,compiled and ran successfully a 64 bit kernel on my 
mips64 platform. Kernel was compiled with support for 32 bit binaries.

I am now trying to insert a module, a standard module from
the kernel tree, and get lots of errors such as:
"Unhandled relocation of type 18 for"
or
"Unhandled relocation of type 18 for <function_name>"

How can this be resolved ?

TIA



[-- Attachment #2: Type: text/html, Size: 1958 bytes --]

insmod failure: "Unhandled relocation" errors

[Gilad Benjamini]

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

Hi,
I've built,compiled and ran successfully a 64 bit kernel on my 
mips64 platform. Kernel was compiled with support for 32 bit binaries.

I am now trying to insert a module, a standard module from
the kernel tree, and get lots of errors such as:
"Unhandled relocation of type 18 for"
or
"Unhandled relocation of type 18 for <function_name>"

How can this be resolved ?

TIA



[-- Attachment #2: Type: text/html, Size: 1958 bytes --]

Re: insmod failure: "Unhandled relocation" errors

[Ralf Baechle]

On Tue, Jan 14, 2003 at 12:06:46PM +0200, Gilad Benjamini wrote:

> I've built,compiled and ran successfully a 64 bit kernel on my 
> mips64 platform. Kernel was compiled with support for 32 bit binaries.
> 
> I am now trying to insert a module, a standard module from
> the kernel tree, and get lots of errors such as:
> "Unhandled relocation of type 18 for"
> or
> "Unhandled relocation of type 18 for <function_name>"
> 
> How can this be resolved ?

Modules are not supported on 64-bit kernel yet.

  Ralf

Re: insmod failure: "Unhandled relocation" errors

[Greg Lindahl]

On Tue, Jan 14, 2003 at 12:06:46PM +0200, Gilad Benjamini wrote:

> I am now trying to insert a module, a standard module from
> the kernel tree, and get lots of errors such as:
> "Unhandled relocation of type 18 for"
> or
> "Unhandled relocation of type 18 for <function_name>"

I'm impressed that it got this far -- let me guess, big endian?
Little endian didn't even get that far last time I tried it.

greg

Re: insmod failure: "Unhandled relocation" errors

[Ralf Baechle]

On Tue, Jan 14, 2003 at 11:14:18AM -0800, Greg Lindahl wrote:

> > I am now trying to insert a module, a standard module from
> > the kernel tree, and get lots of errors such as:
> > "Unhandled relocation of type 18 for"
> > or
> > "Unhandled relocation of type 18 for <function_name>"
> 
> I'm impressed that it got this far -- let me guess, big endian?
> Little endian didn't even get that far last time I tried it.

The modules we also built with the wrong options which is the cause for
these specific error messages.  There was just no point mentioning these
because the actual showstopper was a 32-bit vs. 64-bit problem.

  Ralf

Re: insmod failure: "Unhandled relocation" errors

[Keith Owens]

On Tue, 14 Jan 2003 12:06:46 +0200, 
"Gilad Benjamini" <gilad@riverhead.com> wrote:
>I've built,compiled and ran successfully a 64 bit kernel on my 
>mips64 platform. Kernel was compiled with support for 32 bit binaries.
>
>I am now trying to insert a module, a standard module from
>the kernel tree, and get lots of errors such as:
>"Unhandled relocation of type 18 for"

Type 18 is R_MIPS_64.  modutils does not support 64 bit mips
at all, nobody has sent me any code to handle this architecture.

modutils needs obj/obj_mips64.c.  The config and makefiles have to be
tweaked to handle mips64, including combined 32/64 bit code, as for
sparc32/sparc64.  Does anybody who knows mips64 feel like contributing
the modutils code?

Re: insmod failure: "Unhandled relocation" errors

[Ralf Baechle]

On Wed, Jan 15, 2003 at 10:34:33AM +1100, Keith Owens wrote:

> modutils needs obj/obj_mips64.c.  The config and makefiles have to be
> tweaked to handle mips64, including combined 32/64 bit code, as for
> sparc32/sparc64.  Does anybody who knows mips64 feel like contributing
> the modutils code?

Until recently the big problem with implementing modules support for mips64
was the complete unusability of binutils.  Compared to the complexity of
getting binutils to work what it takes to get modutils to work is plain
trivial ...

  Ralf