From: Aurelien Jarno <aurelien@aurel32.net>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>
Cc: Romain Dolbeau <romain.dolbeau@european-processor-initiative.eu>,
Vincent Chen <vincent.chen@sifive.com>,
Paul Walmsley <paul@pwsan.com>,
Carlos Eduardo de Paula <me@carlosedp.com>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: Error on loading some network Kernel modules
Date: Fri, 31 Jan 2020 21:11:18 +0100 [thread overview]
Message-ID: <20200131201118.GA4121429@aurel32.net> (raw)
In-Reply-To: <CAEn-LToMfm=G80TmGQZefpmKhKvpGy_=XOoBLGU0a_77ahY+_w@mail.gmail.com>
On 2020-01-30 17:20, David Abdurachmanov wrote:
> On Thu, Jan 30, 2020 at 4:00 AM Paul Walmsley <paul@pwsan.com> wrote:
> >
> > On Tue, 28 Jan 2020, Carlos Eduardo de Paula wrote:
> >
> > > I currently run stock Kernel 5.5.0-rc7 on my Unleashed board with most
> > > network features I need baked into the kernel instead of modules.
> > >
> > > I tried building a kernel with these network features as modules but
> > > when loading some of them I got this error:
> > >
> > > root@unleashed:~# uname -a
> > > Linux unleashed 5.5.0-rc7-dirty #4 SMP Fri Jan 24 18:16:43 -02 2020
> > > riscv64 GNU/Linux
> > >
> > > root@unleashed:~# modprobe br_netfilter
> > > [ 139.290533] br_netfilter: target ffffffe0000422d8 can not be
> > > addressed by the 32-bit offset from PC = 000000003dfd6deb
> >
> > This is a known issue:
> >
> > https://lore.kernel.org/linux-riscv/1572281840733.3517@european-processor-initiative.eu/
> >
> > https://lore.kernel.org/linux-riscv/20191029105055.GA20736@aurel32.net/#r
> >
> > Vincent is looking into it and I expect there will be a fix soon.
> >
>
> Is this patch solving the problem?
>
> https://github.com/bjoto/linux/commit/8a56d1c8e8e91c1bc3893946d52b9217c96e1589
I have just tried that patch on top of a 5.4.13 kernel, and I confirm it
fixes the issue. Thanks!
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2020-01-31 20:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 19:22 Error on loading some network Kernel modules Carlos Eduardo de Paula
2020-01-30 3:00 ` Paul Walmsley
2020-01-30 16:20 ` David Abdurachmanov
2020-01-31 14:12 ` Carlos Eduardo de Paula
2020-01-31 20:11 ` Aurelien Jarno [this message]
2020-02-01 7:52 ` Anup Patel
2020-02-01 13:59 ` Alex Ghiti
2020-02-02 14:10 ` Anup Patel
2020-02-02 15:21 ` Troy Benjegerdes
2020-02-02 16:27 ` Romain Dolbeau
2020-02-03 10:04 ` Vincent Chen
2020-02-04 3:55 ` Zong Li
2020-02-04 6:50 ` Alex Ghiti
2020-02-04 7:19 ` Zong Li
2020-02-04 9:32 ` Alexandre Ghiti
2020-02-04 10:46 ` Vincent Chen
2020-02-04 11:30 ` Anup Patel
2020-02-04 14:03 ` Vincent Chen
2020-02-04 19:10 ` Alex Ghiti
[not found] ` <a55f265e-71b2-5ebb-b079-6345007a442e@ghiti.fr>
2020-02-05 3:22 ` Vincent Chen
2020-02-05 4:24 ` Anup Patel
2020-02-05 10:37 ` Vincent Chen
2020-02-07 14:39 ` Vincent Chen
2020-02-07 14:51 ` Vincent Chen
2020-02-10 6:37 ` Alex Ghiti
2020-02-10 9:53 ` Vincent Chen
2020-02-19 6:46 ` Alex Ghiti
2020-02-19 7:30 ` Vincent Chen
2020-02-04 17:48 ` Romain Dolbeau
2020-02-03 20:57 ` Alex Ghiti
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=20200131201118.GA4121429@aurel32.net \
--to=aurelien@aurel32.net \
--cc=david.abdurachmanov@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=me@carlosedp.com \
--cc=paul@pwsan.com \
--cc=romain.dolbeau@european-processor-initiative.eu \
--cc=vincent.chen@sifive.com \
/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