All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Soanes <ians@lineo.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Shay Deloya <shay@jungo.com>,
	"'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: Insmod messages and modules space
Date: Tue, 10 Apr 2001 09:55:16 +0100	[thread overview]
Message-ID: <3AD2CA74.DCC850EF@lineo.com> (raw)
In-Reply-To: 20010409211447.A18894@bacchus.dhis.org

Ralf Baechle wrote:
> 
> On Mon, Apr 09, 2001 at 08:10:16PM +0200, Shay Deloya wrote:
> 
> > 1.Should text segment of module after insmod be in KSEG2 or KUSEG ?
> > I've notices that the module address after insmod are c0... instead of 80...
> > Is it insmod Bug  ?
> 
> It's a sign of insmod working properly :)
> 
> > 2. I keep getting in insmod of busybox pkg , "relocation overflow" message
> > especially on printk symbols , when I debug the code, changing some function
> > declaration from static int func () to int func()  , makes the module to
> > insert correctly , anyone ?
> 
> Two possibilities, either you're using a too old and broken version of
> modutils or you used inapropriate options to compile your module.
> 

Compiling with -mlong-calls worked for me when I had the same problem
(modutils 2.4.5). Relinking the module with 'ld -r -o new_mod.o
orig_mod.o' was useful too ...it worked around some 'exceeds
local_symtab_size' messages.

Ian

  reply	other threads:[~2001-04-10  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09 18:10 Insmod messages and modules space Shay Deloya
2001-04-09 19:14 ` Ralf Baechle
2001-04-10  8:55   ` Ian Soanes [this message]
2001-04-23 22:57     ` Keith Owens
2001-04-24  8:22       ` Ian Soanes

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=3AD2CA74.DCC850EF@lineo.com \
    --to=ians@lineo.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=shay@jungo.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.