From: James Bottomley <James.Bottomley@SteelEye.com>
To: Randolph Chung <randolph@tausq.org>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] kernel module relocation bug
Date: 29 Nov 2004 09:32:11 -0600 [thread overview]
Message-ID: <1101742338.1714.8.camel@mulgrave> (raw)
In-Reply-To: <20041127064710.GL9148@tausq.org>
On Sat, 2004-11-27 at 00:47, Randolph Chung wrote:
> currently the kernel module loader does not support long branch stubs.
> using the debian 2.6.8-1 kernel, when loading the ipv6 module, i see:
>
> legolas[6:43] linux-2.6% sudo modprobe ipv6
> FATAL: Error inserting ipv6 (/lib/modules/2.6.8-1-32-smp/kernel/net/ipv6/ipv6.ko): Invalid module format
>
> in syslog, i get:
> module ipv6 relocation of symbol fold_prot_inuse is out of range (0x3ffeffe2 in 17 bits)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-11-29 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 6:47 [parisc-linux] kernel module relocation bug Randolph Chung
2004-11-29 15:32 ` James Bottomley [this message]
2004-11-29 15:33 ` James Bottomley
2004-11-29 19:27 ` Ulrich Teichert
2004-11-29 19:46 ` Randolph Chung
2004-11-29 22:51 ` Ulrich Teichert
2004-11-29 23:46 ` John David Anglin
2004-12-02 21:54 ` [parisc-linux] Userland relocation problems resolved (was: kernel module relocation bug) Ulrich Teichert
2004-12-02 22:51 ` [parisc-linux] Re: Userland relocation problems resolved (was: kernel module relocat John David Anglin
2004-11-29 23:53 ` [parisc-linux] kernel module relocation bug John David Anglin
2004-11-29 23:54 ` Randolph Chung
2004-11-29 23:57 ` Randolph Chung
2004-11-30 0:08 ` John David Anglin
2004-11-30 0:11 ` James Bottomley
2004-11-30 0:23 ` John David Anglin
2004-11-30 1:18 ` James Bottomley
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=1101742338.1714.8.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.org \
/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