From: Thorsten Kranzkowski <dl8bcu@dl8bcu.de>
To: "Måns Rullgård" <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Relocation overflow with modules on Alpha
Date: Tue, 6 Jan 2004 00:44:35 +0000 [thread overview]
Message-ID: <20040106004435.A3228@Marvin.DL8BCU.ampr.org> (raw)
In-Reply-To: <yw1xy8sn2nry.fsf@ford.guide>; from mru@kth.se on Mon, Jan 05, 2004 at 02:21:37AM +0100
On Mon, Jan 05, 2004 at 02:21:37AM +0100, Måns Rullgård wrote:
>
> I compiled Linux 2.6.0 for Alpha, and it mostly works, except the
> somewhat large modules. They fail to load with the message
> "Relocation overflow vs section 17", or some other section number.
> I've seen this with scsi-mod, nfsd, snd-page-alloc and possibly some
> more. Compiling them statically works. What's going on?
I saw a similar thing, but I'm compiling everything statically:
: relocation truncated to fit: BRADDR .init.text
init/built-in.o(.text+0xf10): In function `inflate_codes':
Disabling a not so important subsystem (sound) helped for the time being.
It seems my kernel crossed the 4 MB barrier in consumed RAM and possibly
some relocation type(s) can't cope with that. Time to use -fpic or
some such?
Thorsten
--
| Thorsten Kranzkowski Internet: dl8bcu@dl8bcu.de |
| Mobile: ++49 170 1876134 Snail: Kiebitzstr. 14, 49324 Melle, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, dl8bcu@marvin.dl8bcu.ampr.org [44.130.8.19] |
next prev parent reply other threads:[~2004-01-06 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 1:21 Måns Rullgård
2004-01-06 0:44 ` Thorsten Kranzkowski [this message]
2004-01-06 0:59 ` Måns Rullgård
2004-01-08 15:15 ` Ivan Kokshaysky
2004-01-08 22:46 ` Thorsten Kranzkowski
2004-01-08 14:10 ` [patch 2.6] " Ivan Kokshaysky
[not found] <1arJl-l5-9@gated-at.bofh.it>
[not found] ` <1aNAg-5UM-29@gated-at.bofh.it>
[not found] ` <1bKho-37e-25@gated-at.bofh.it>
2004-01-08 16:18 ` Pascal Schmidt
2004-01-08 19:21 ` Ivan Kokshaysky
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=20040106004435.A3228@Marvin.DL8BCU.ampr.org \
--to=dl8bcu@dl8bcu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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
all inboxes | Powered by JetHome®