From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Tracy Subject: Re: Relocation (type 4) overflow on alpha for big module Date: Sun, 14 Oct 2018 18:14:20 -0500 Message-ID: <20181014231420.GA17263@gherkin.frus.com> References: <5bc11e00-258d-a6ea-fe63-ddcfdb847071@linux.ee> <20181014173306.GA14639@gherkin.frus.com> <20181014184148.m6jb5ohb5onu6c3k@tower> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20181014184148.m6jb5ohb5onu6c3k@tower> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Michael Cree , Meelis Roos , linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org On Mon, Oct 15, 2018 at 07:41:48AM +1300, Michael Cree wrote: > On Sun, Oct 14, 2018 at 12:33:06PM -0500, Bob Tracy wrote: > > On Sun, Oct 14, 2018 at 10:07:13AM +0300, Meelis Roos wrote: > > > I decided to try btrfs on one of my alphas and got a surprise - btrfs module does not load: > > > > Confirmed on a PWS 433au running 4.19.0-rc6 with latest "sid" toolchain. > > Known and long-standing problem in the Alpha kernel module loader. > Requires extra code implmented to support loading such large modules > which no one has done. Workaround is to build the kernel with such > modules (e.g. radeon, btrfs) in-built. ACK on the workaround. Never noticed the problem with, per your example, the radeon driver because I seldom build a driver as a module for a piece of hardware (or filesystem type) that's present at boot and won't be removed. --Bob