Re: Can't allocate memory when loading a module 2.5.48-bk

• Next message: Eric W. Biederman: "Re: [ANNOUNCE][CFT] kexec for v2.5.48 && kexec-tools-1.7 -- Success Story!"
• Previous message: Greg KH: "[BK PATCH] USB changes for 2.5.48"
• In reply to: Greg KH: "Can't allocate memory when loading a module 2.5.48-bk"
• Next in thread: Juan M. de la Torre: "Re: Can't allocate memory when loading a module 2.5.48-bk"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Greg KH wrote:
> With Linus's latest bk tree (plus some USB patches) I get the following
> error when trying to load the parport.o module:
>
> # modprobe parport
> FATAL: Error inserting /lib/modules/2.5.48/kernel/parport.o: Cannot allocate memory
>
> Any ideas?

Tag some init code with __init

At least stock 2.5.48 tries to happily allocate zero bytes for init section,
and gets a null pointer. That 'error' is then propagated to user space.

Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Eric W. Biederman: "Re: [ANNOUNCE][CFT] kexec for v2.5.48 && kexec-tools-1.7 -- Success Story!"
• Previous message: Greg KH: "[BK PATCH] USB changes for 2.5.48"
• In reply to: Greg KH: "Can't allocate memory when loading a module 2.5.48-bk"
• Next in thread: Juan M. de la Torre: "Re: Can't allocate memory when loading a module 2.5.48-bk"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:31 EST