From: Aurelien Jarno <aurelien@aurel32.net>
To: Romain Dolbeau <romain.dolbeau@european-processor-initiative.eu>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Palmer Dabbelt <palmer@sifive.com>,
"romain@dolbeau.org" <romain@dolbeau.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: 32-bits offset issue preventing module to load,
Date: Tue, 29 Oct 2019 11:50:55 +0100 [thread overview]
Message-ID: <20191029105055.GA20736@aurel32.net> (raw)
In-Reply-To: <1572281840733.3517@european-processor-initiative.eu>
Hi,
On 2019-10-28 16:57, Romain Dolbeau wrote:
> Hello,
>
> I have a Fedora RISC-V running fine in QEMU, using packaged kernel "5.4.0-0.rc4.git0.300.1.riscv64.fc32.riscv64".
> Some modules won't load, such as openvswitch:
>
> #####
> $ sudo modprobe openvswitch ; dmesg | tail -1
> modprobe: ERROR: could not insert 'openvswitch': Invalid argument
> [ 227.833317] openvswitch: target ffffffe0000d1fd8 can not be addressed by the 32-bit offset from PC = 00000000bcd11221
> #####
The same problem also happens on a 5.2.17 kernel (from the Debian
package) with the scsi_mod loading (dependency of virtio_scsi):
[ 330.737763] scsi_mod: target ffffffe00007fa20 can not be addressed by the 32-bit offset from PC = 00000000e0712647
> The message is explicit, a 32-bits offset is not enough to access the data @ 0xffffffe0000d1fd8 from 0x00000000bcd11221. The relevant (I think) part of the System.map is:
>
> #####
> /usr/src/kernels/5.4.0-0.rc4.git0.300.1.riscv64.fc32.riscv64/System.map:ffffffe0000d1fd8 D __init_end
> /usr/src/kernels/5.4.0-0.rc4.git0.300.1.riscv64.fc32.riscv64/System.map:ffffffe0000d1fd8 D __per_cpu_end
> /usr/src/kernels/5.4.0-0.rc4.git0.300.1.riscv64.fc32.riscv64/System.map:ffffffe0000d1fd8 T _stext
> /usr/src/kernels/5.4.0-0.rc4.git0.300.1.riscv64.fc32.riscv64/System.map:ffffffe0000d1fd8 T _text
> /usr/src/kernels/5.4.0-0.rc4.git0.300.1.riscv64.fc32.riscv64/System.map:ffffffe0000d1fd8 t trace_initcall_finish_cb
> #####
In my case, it points to the same symbols:
ffffffe00007fa18 D __init_end
ffffffe00007fa18 D __per_cpu_end
ffffffe00007fa18 T _stext
ffffffe00007fa18 T _text
ffffffe00007fa18 t trace_initcall_finish_cb
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-10-29 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 16:57 32-bits offset issue preventing module to load, Romain Dolbeau
2019-10-29 10:50 ` Aurelien Jarno [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=20191029105055.GA20736@aurel32.net \
--to=aurelien@aurel32.net \
--cc=aou@eecs.berkeley.edu \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=romain.dolbeau@european-processor-initiative.eu \
--cc=romain@dolbeau.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.