From: Bob Tracy <rct@gherkin.frus.com>
To: Michael Cree <mcree@orcon.net.nz>, debian-alpha@lists.debian.org
Cc: linux-kernel@vger.kernel.org
Subject: [BUG] alpha: module xxx: Unknown relocation: 1
Date: Tue, 11 Apr 2017 21:59:35 -0500 [thread overview]
Message-ID: <20170412025935.GA10065@gherkin.frus.com> (raw)
In-Reply-To: <20170411215716.GA29795@gherkin.frus.com>
(Adding linux-kernel to the distribution. The issue seems to be
architecture-specific, but I'm trying to understand what broke.)
The 4.10-rc1 patch set made fairly extensive modifications to
"a/kernel/module.c" (I'm leaving the "a" there so there's no doubt I
mean the top-level "kernel/module.c" file and not any of the
architecture-specific ones).
One of the changes was to replace an include of <asm/uaccess.h> with
<linux/uaccess.h>. This is potentially significant because of the
mod we made to alpha's <asm/uaccess.h> to fix the BRSGP relocation
error on __copy_user() issue.
Bottom line is, no kernel I've built since 4.9 can load a module. All
attempts to load a module result in the error message emitted by
"arch/alpha/kernel/module.c" as follows:
module XXX: Unknown relocation: 1
I'll start attempting to revert the recent module patches to see if that
helps. If anyone reading this knows what's happening, feel free to
weigh-in before I spend too much time rebuilding kernels on a slow
machine.
--Bob
next parent reply other threads:[~2017-04-12 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170410004755.GA22356@gherkin.frus.com>
[not found] ` <20170410094250.gxcne7imso4u2vjx@tower>
[not found] ` <20170411034242.GA27395@gherkin.frus.com>
[not found] ` <20170411061232.bchlfc73lqx2z2cy@tower>
[not found] ` <20170411215716.GA29795@gherkin.frus.com>
2017-04-12 2:59 ` Bob Tracy [this message]
2017-04-12 5:57 ` Helge Deller
2017-04-12 7:36 ` Michael Cree
2017-04-13 3:46 ` Bob Tracy
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=20170412025935.GA10065@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
/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
all inboxes | Powered by JetHome®