Linux-parisc archive on lore.kernel.org
 help / color / Atom feed
From: John David Anglin <dave.anglin@bell.net>
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 09:50:45 -0400
Message-ID: <9c3811a6-bbce-d3fc-8a3d-8d85c242915f@bell.net> (raw)
In-Reply-To: <20190608145201.56c667f5@wim.jer>

On 2019-06-08 8:52 a.m., Jeroen Roovers wrote:
> Second resend. Not sure why e-mail from my Gentoo account and private
> account never arrive. Originally sent on 21 May 2019, but I still see
> this issue in 5.2.0-rc3-JeR-00077-g16d72dd4891f. I attached the kernel
> config in earlier attempts but I am leaving that out this time.
> 
> 
> <Forwarded message:> 
> 
> 
> # 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

Relocation 72 is R_PARISC_PCREL64.  It would be created in assembler using
something like:

	.dword symbol-.

> 
> # modprobe -v nf_conntrack
> insmod /lib/modules/5.2.0-rc1-JeR/kernel/net/netfilter/nf_conntrack.ko
> modprobe: ERROR: could not insert 'nf_conntrack': Exec format error
> 
> dmesg:
> module nf_conntrack: Unknown relocation: 72
> 
> Note that other modules are loaded properly. Any ideas?

You could find how it's created by looking at assembler for nf_conntrack.

Dave
-- 
John David Anglin  dave.anglin@bell.net

      parent reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08 12:52 Jeroen Roovers
2019-06-08 13:41 ` Helge Deller
2019-06-08 13:51   ` Jeroen Roovers
2019-06-08 14:32   ` Helge Deller
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 ` John David Anglin [this message]

Reply instructions:

You may reply publically 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=9c3811a6-bbce-d3fc-8a3d-8d85c242915f@bell.net \
    --to=dave.anglin@bell.net \
    --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

Linux-parisc archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-parisc/0 linux-parisc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-parisc linux-parisc/ https://lore.kernel.org/linux-parisc \
		linux-parisc@vger.kernel.org linux-parisc@archiver.kernel.org
	public-inbox-index linux-parisc


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-parisc


AGPL code for this site: git clone https://public-inbox.org/ public-inbox