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
