From: Helge Deller <deller@gmx.de>
To: Jeroen Roovers <jer@gentoo.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Cc: hppa@gentoo.org
Subject: Re: [RESEND V2] modprobe: ERROR: could not insert 'ipv6': Exec format error / module ipv6: Unknown relocation: 72
Date: Sat, 8 Jun 2019 16:32:47 +0200 [thread overview]
Message-ID: <487d5cc9-742b-82f1-604c-f24848c1580c@gmx.de> (raw)
In-Reply-To: <f3b34093-1b01-f321-3b98-6708cdc25434@gmx.de>
On 08.06.19 15:41, Helge Deller wrote:
> On 08.06.19 14:52, Jeroen Roovers wrote:
>> # modprobe -v ipv6
>> insmod /lib/modules/5.2.0-rc1-JeR/kernel/net/ipv6/ipv6.ko
>> modprobe: ERROR: could not insert 'ipv6': Exec format error
>> dmesg:
>> module ipv6: Unknown relocation: 72
>
> You could try attached untested patch.
> I still wonder why you get R_PARISC_PCREL64 relocations.
> Can you send your .config ?
-> https://dev.gentoo.org/~jer/c8000.config
Thanks!
The R_PARISC_PCREL64 relocations are in the __jump_table section,
so they were introduced by this commit:
parisc: Add static branch and JUMP_LABEL feature
See:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=62217beb394e654bbd2bb87c533dadd2d8bf62c6
Jeroen, I think the last patch I sent to you should help...
Helge
next prev parent reply other threads:[~2019-06-08 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 12:52 [RESEND V2] modprobe: ERROR: could not insert 'ipv6': Exec format error / module ipv6: Unknown relocation: 72 Jeroen Roovers
2019-06-08 13:41 ` Helge Deller
2019-06-08 13:51 ` Jeroen Roovers
2019-06-08 14:32 ` Helge Deller [this message]
2019-06-08 14:49 ` Jeroen Roovers
2019-06-08 18:04 ` [PATCH] parisc: Fix module loading error with JUMP_LABEL feature Helge Deller
2019-06-08 13:50 ` [RESEND V2] modprobe: ERROR: could not insert 'ipv6': Exec format error / module ipv6: Unknown relocation: 72 John David Anglin
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=487d5cc9-742b-82f1-604c-f24848c1580c@gmx.de \
--to=deller@gmx.de \
--cc=hppa@gentoo.org \
--cc=jer@gentoo.org \
--cc=linux-parisc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).