linux-mips
[Top] [All Lists]

Re: module loading on 64-bit kernel

To: Markus Dahms <mad@automagically.de>
Subject: Re: module loading on 64-bit kernel
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 19 Jul 2005 15:48:42 -0400
Cc: linux-mips@linux-mips.org
In-reply-to: <20050719183546.GA3923@gaspode.automagically.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050719183546.GA3923@gaspode.automagically.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.2.1i
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

<Prev in Thread] Current Thread [Next in Thread>