From: Daniel Jacobowitz <dan@debian.org>
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: Mon, 25 Feb 2002 20:13:27 -0500 [thread overview]
Message-ID: <20020225201327.A2427@nevyn.them.org> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIGEMACFAA.mdharm@momenco.com>
On Mon, Feb 25, 2002 at 12:30:38PM -0800, Matthew Dharm wrote:
> Well, that fixes it. The driver works out-of-the-box with just some
> minor makefile modifications.
>
> 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.
>
> I'm more than willing to help, as I seem to be the only person with a
> 100% reproducable situation. But I really have no idea even where to
> begin looking... my expertise ends right about at objdump, and even
> then I'm not certain how some of that data should look for loadable
> modules.
Silly question... was the module built with the correct flags? Look at
a command line; does it have all the same options as when you build a
module in the kernel source?
I bet something's missing. Probably -G 0...
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-26 2:14 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 [this message]
2002-02-26 1:18 ` Matthew Dharm
2002-02-26 10:31 ` Tommy S. Christensen
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=20020225201327.A2427@nevyn.them.org \
--to=dan@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox