All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tommy S. Christensen" <tommy.christensen@eicon.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: Kevin Paul Herbert <kph@ayrnetworks.com>,
	Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: Is this a toolchain bug?
Date: Tue, 26 Feb 2002 11:31:03 +0100	[thread overview]
Message-ID: <3C7B63E7.8DFF9D89@eicon.com> (raw)
In-Reply-To: NEBBLJGMNKKEEMNLHGAIGEMACFAA.mdharm@momenco.com

Matthew Dharm wrote:
> 
> So, we've got a problem somewhere in the module handling.  Either the
> symbol wasn't being relocated properly, or it wasn't being allocated
> properly, or something.  I'm not an expert in this region of the
> kernel, but my guess is that we're going to see this more and more
> often, so someone with a clue should take a look at this.

To me, this looks like a problem with common symbols that I have run
into a couple of times (I think it was in i2o).

Compiling with -fno-common or linking with -d worked for me.
(Or avoid having uninitialized global variables.)

I guess insmod should actually complain in this case ?!

 -Tommy

  parent reply	other threads:[~2002-02-26 11:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  1:57 Is this a toolchain bug? Matthew Dharm
2002-02-24  2:06 ` Daniel Jacobowitz
2002-02-25  2:30   ` Matthew Dharm
2002-02-25 18:36 ` Kevin Paul Herbert
2002-02-25 19:54   ` Matthew Dharm
2002-02-25 20:30   ` Matthew Dharm
2002-02-26  1:13     ` Daniel Jacobowitz
2002-02-26  1:18       ` Matthew Dharm
2002-02-26 10:31     ` Tommy S. Christensen [this message]
2002-02-26 20:29       ` Matthew Dharm

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=3C7B63E7.8DFF9D89@eicon.com \
    --to=tommy.christensen@eicon.com \
    --cc=kph@ayrnetworks.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mdharm@momenco.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.