Date: Tue, 11 Apr 2017 21:59:35 -0500
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
Message-ID: <20170412025935.GA10065@gherkin.frus.com>
References: <20170410004755.GA22356@gherkin.frus.com>
 <20170410094250.gxcne7imso4u2vjx@tower>
 <20170411034242.GA27395@gherkin.frus.com>
 <20170411061232.bchlfc73lqx2z2cy@tower>
 <20170411215716.GA29795@gherkin.frus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170411215716.GA29795@gherkin.frus.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1024
Lines: 25

(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