From: Bob Tracy <rct@gherkin.frus.com>
To: Michael Cree <mcree@orcon.net.nz>, Meelis Roos <mroos@linux.ee>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Relocation (type 4) overflow on alpha for big module
Date: Sun, 14 Oct 2018 18:14:20 -0500 [thread overview]
Message-ID: <20181014231420.GA17263@gherkin.frus.com> (raw)
In-Reply-To: <20181014184148.m6jb5ohb5onu6c3k@tower>
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
prev parent reply other threads:[~2018-10-14 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 7:07 Relocation (type 4) overflow on alpha for big module Meelis Roos
2018-10-14 17:33 ` Bob Tracy
2018-10-14 18:41 ` Michael Cree
2018-10-14 23:14 ` Bob Tracy [this message]
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=20181014231420.GA17263@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=mroos@linux.ee \
/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