module loading on 64-bit kernel

module loading on 64-bit kernel

[Markus Dahms]

Hello together,

do I need other module-init-tools for a 64-bit kernel than I need for
32-bit?
When trying to load a module I get the following output:
| insmod: error inserting \
| '/lib/modules/2.6.13-rc3-mad-mips-1-64/kernel/fs/isofs/isofs.ko': -1 \
| Cannot allocate memory

in dmesg:
| allocation failed: out of vmalloc space - use vmalloc=<size> to increase \
| size.

It happens with every module. If I'd need other tools these messages are
confusing. I didn't try "vmalloc=..." as I think module loading wouldn't
be "disabled" in such a way by default...

If I need special 64-bit module-init-tools, is there a way to build them
without a 64-bit glibc as all of my userspace stuff is 32-bit?

Markus

Re: module loading on 64-bit kernel

[Thiemo Seufer]

Markus Dahms wrote:
> Hello together,
> 
> do I need other module-init-tools for a 64-bit kernel than I need for
> 32-bit?
> When trying to load a module I get the following output:
> | insmod: error inserting \
> | '/lib/modules/2.6.13-rc3-mad-mips-1-64/kernel/fs/isofs/isofs.ko': -1 \
> | Cannot allocate memory
> 
> in dmesg:
> | allocation failed: out of vmalloc space - use vmalloc=<size> to increase \
> | size.

This seems to be a bug which crept in for (at least) 64bit Indy kernels
in IIRC 2.6.12-rc3.

> It happens with every module. If I'd need other tools these messages are
> confusing. I didn't try "vmalloc=..." as I think module loading wouldn't
> be "disabled" in such a way by default...

It happens also for any significant memory pressure.


Thiemo

Re: module loading on 64-bit kernel

[Ralf Baechle]

On Tue, Jul 19, 2005 at 08:35:46PM +0200, Markus Dahms wrote:

> do I need other module-init-tools for a 64-bit kernel than I need for
> 32-bit?
> When trying to load a module I get the following output:
> | insmod: error inserting \
> | '/lib/modules/2.6.13-rc3-mad-mips-1-64/kernel/fs/isofs/isofs.ko': -1 \
> | Cannot allocate memory
> 
> in dmesg:
> | allocation failed: out of vmalloc space - use vmalloc=<size> to increase \
> | size.
> 
> It happens with every module. If I'd need other tools these messages are
> confusing. I didn't try "vmalloc=..." as I think module loading wouldn't
> be "disabled" in such a way by default...
> 
> If I need special 64-bit module-init-tools, is there a way to build them
> without a 64-bit glibc as all of my userspace stuff is 32-bit?

You don't need. In fact the nice thing about module-init-tools is that
they're file format agnostic so didn't need any changes for MIPS porting.

  Ralf

Re: module loading on 64-bit kernel

[Stephen P. Becker]

> This seems to be a bug which crept in for (at least) 64bit Indy kernels
> in IIRC 2.6.12-rc3.

I'm fairly certain it happened with the initial 2.6.11-rc1 import.  I'd 
have to go back and double check to be 100% on that.

>>It happens with every module. If I'd need other tools these messages are
>>confusing. I didn't try "vmalloc=..." as I think module loading wouldn't
>>be "disabled" in such a way by default...
> 
> 
> It happens also for any significant memory pressure.

...including significant use of dd, mounting of ricerfs partitions, 
mounting of swap, etc.

-Steve