From: Alexander Holler <holler@ahsoftware.de>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux@arm.linux.org.uk
Subject: ARM: relocation out of range (when loading a module)
Date: Mon, 10 Jan 2011 19:16:04 +0100 [thread overview]
Message-ID: <4D2B4CE4.9080309@ahsoftware.de> (raw)
Hello,
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):
----------------------------
# modprobe ipv6
modprobe: 'kernel/net/ipv6/ipv6.ko': invalid module format
# dmesg | tail -n 1
[ 107.327672] ipv6: relocation out of range, section 2 reloc 0 sym
'snmp_mib_free'
----------------------------
To compile the kernel I've used gcc 4.5.2 and binutils 2.21.
If I apply the patch found at
http://lists.arm.linux.org.uk/lurker/message/20100729.090437.85f82ebd.en.html
the output from dmesg will be
----------------------------
[ 58.211776] ipv6: section 2 reloc 0 sym 'snmp_mib_free': relocation
28 out of range (0xbf0000a4 -> 0xc11b4858)
----------------------------
I don't know much about how the memory is organized and the relocation
is done for arm, but reading that output it seems the 32MB limit is
reached. Is that because of the initramfs (just speculating) and is
there a workaround to still include such an initramfs in the kernel?
An excerpt from my config:
----------------------------
CONFIG_ARM_THUMB=y
...
# CONFIG_HIGHMEM is not set
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
# CONFIG_HIGHMEM is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_PAGEFLAGS_EXTENDED=y
----------------------------
Regards,
Alexander
next reply other threads:[~2011-01-10 18:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 18:16 Alexander Holler [this message]
2011-01-10 22:26 ` ARM: relocation out of range (when loading a module) Nicolas Pitre
2011-01-11 6:34 ` Alexander Holler
2011-01-11 15:17 ` Alexander Holler
2011-01-11 15:57 ` Russell King - ARM Linux
2011-01-11 16:02 ` Nicolas Pitre
2011-01-11 15:46 ` Rabin Vincent
2011-01-11 15:59 ` Russell King - ARM Linux
2011-01-12 3:00 ` Alexander Holler
2011-01-12 16:05 ` Dave Martin
2011-01-12 16:23 ` Russell King - ARM Linux
2011-01-12 18:28 ` Nicolas Pitre
2011-01-12 18:42 ` Russell King - ARM Linux
2011-01-12 18:55 ` Nicolas Pitre
2011-01-25 8:44 ` Sachin Verma
2011-01-25 13:23 ` Catalin Marinas
2011-01-27 5:43 ` Nicolas Pitre
2011-02-10 15:43 ` Russell King - ARM Linux
2011-02-10 19:41 ` Nicolas Pitre
2011-02-11 9:31 ` Dave Martin
2011-02-11 9:38 ` Russell King - ARM Linux
2011-02-11 9:45 ` Dave Martin
2011-02-11 13:55 ` Nicolas Pitre
2011-02-11 13:51 ` Nicolas Pitre
2011-02-11 14:25 ` Dave Martin
2011-02-11 14:42 ` Russell King - ARM Linux
2011-02-12 19:52 ` Nicolas Pitre
2011-01-13 5:50 ` Alexander Holler
2011-01-13 10:04 ` Russell King - ARM Linux
2011-01-13 14:36 ` Alexander Holler
2011-01-12 16:25 ` Matthieu CASTET
2011-01-12 16:38 ` Russell King - ARM Linux
2011-01-11 16:01 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D2B4CE4.9080309@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox