From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756149Ab1AKPRf (ORCPT ); Tue, 11 Jan 2011 10:17:35 -0500 Received: from h1047321.serverkompetenz.net ([85.214.67.163]:50621 "EHLO mail.ahsoftware.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756093Ab1AKPRe (ORCPT ); Tue, 11 Jan 2011 10:17:34 -0500 Message-ID: <4D2C7484.3050309@ahsoftware.de> Date: Tue, 11 Jan 2011 16:17:24 +0100 From: Alexander Holler User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc13 Lightning/1.0b3pre Thunderbird/3.1.7 MIME-Version: 1.0 To: Nicolas Pitre CC: linux-kernel@vger.kernel.org, linux@arm.linux.org.uk Subject: Re: ARM: relocation out of range (when loading a module) References: <4D2B4CE4.9080309@ahsoftware.de> <4D2BFA08.5030104@ahsoftware.de> In-Reply-To: <4D2BFA08.5030104@ahsoftware.de> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 11.01.2011 07:34, schrieb Alexander Holler: > Am 10.01.2011 23:26, schrieb Nicolas Pitre: >> On Mon, 10 Jan 2011, Alexander Holler wrote: >> >>> I've build a kernel 2.6.37 for an armv5-device which includes an >>> initramfs of >>> about 16MB (uncompressed, result is a kernel of about 6MB) and I now >>> getting >>> errors when trying to load a module (which is included in that >>> initramfs): >> >> Do you really need to have such a bit initramfs? > > Not really, but it is handier to use than a separate file. > >> What you can do to work around this issue is to load your initramfs >> separately as a initrd ramdisk image. , and not combine it with the >> kernel image. > > Point is that I would like to understand why including an initramfs has > such consequences. > > I have to search for some pictures which are explaining the memory > layout (never had any interested in that before). > > I assume some memory near the kernel is reserved for the modules and an > initramfs will come inbetween the kernel and the reserved memory for > modules. Thinking a bit more about that (for me unexcpected) "relocation out of range" error when loading a module, I'm curious if there could be other conditions which would lead to that error. Especially conditions which could be generated by the userspace or remote from some network. Regards, Alexander