From: Palmer Dabbelt <palmer@dabbelt.com>
To: schwab@linux-m68k.org
Cc: aou@eecs.berkeley.edu, alexghiti@rivosinc.com, alex@ghiti.fr,
linux-kernel@vger.kernel.org, npiggin@gmail.com,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v8 1/3] riscv: Introduce CONFIG_RELOCATABLE
Date: Fri, 12 May 2023 11:41:19 -0700 (PDT) [thread overview]
Message-ID: <mhng-c528747d-5f47-4e42-b6db-f9db4e756ff9@palmer-ri-x1c9a> (raw)
In-Reply-To: <87ttwi91g0.fsf@igel.home>
On Thu, 11 May 2023 11:18:23 PDT (-0700), schwab@linux-m68k.org wrote:
> On Mai 09 2023, Alexandre Ghiti wrote:
>
>> On 5/9/23 21:07, Andreas Schwab wrote:
>>> That does not work with UEFI booting:
>>>
>>> Loading Linux 6.4.0-rc1-1.g668187d-default ...
>>> Loading initial ramdisk ...
>>> Unhandled exception: Instruction access fault
>>> EPC: ffffffff80016d56 RA: 000000008020334e TVAL: 0000007f80016d56
>>> EPC: ffffffff002d1d56 RA: 00000000004be34e reloc adjusted
>>> Unhandled exception: Load access fault
>>> EPC: 00000000fff462d4 RA: 00000000fff462d0 TVAL: ffffffff80016d56
>>> EPC: 00000000802012d4 RA: 00000000802012d0 reloc adjusted
>>>
>>> Code: c825 8e0d 05b3 40b4 d0ef 0636 7493 ffe4 (d783 0004)
>>> UEFI image [0x00000000fe65e000:0x00000000fe6e3fff] '/efi\boot\bootriscv64.efi'
>>> UEFI image [0x00000000daa82000:0x00000000dcc2afff]
>>>
>>
>> I need more details please, as I have a UEFI bootflow and it works great
>> (KASLR is based on a relocatable kernel and works fine in UEFI too).
>
> It also crashes without UEFI. Disabling CONFIG_RELOCATABLE fixes that.
> This was tested on the HiFive Unmatched board.
> The kernel image I tested is available from
> <https://download.opensuse.org/repositories/Kernel:/HEAD/RISCV/>. The
> same kernel with CONFIG_RELOCATABLE disabled is available from
> <https://download.opensuse.org/repositories/home:/Andreas_Schwab:/riscv:/kernel/standard/>.
Sorry I missed this earlier, there's been some other reports of boot
failures on rc1 showing up but those were all a lot more vague. Just
setting CONFIG_RELOCATABLE=y doesn't manifest a boot failure on QEMU on
my end and I don't have an UNmatched floating around.
Alex says he's going to look into it (and IIRC he has my Unmatched...).
next prev parent reply other threads:[~2023-05-12 18:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 14:36 [PATCH v8 0/3] Introduce 64b relocatable kernel Alexandre Ghiti
2023-02-15 14:36 ` [PATCH v8 1/3] riscv: Introduce CONFIG_RELOCATABLE Alexandre Ghiti
2023-02-22 12:29 ` Alexandre Ghiti
2023-02-24 15:58 ` Björn Töpel
2023-03-22 18:25 ` Nick Desaulniers
2023-03-23 20:01 ` Fangrui Song
2023-03-24 10:34 ` Alexandre Ghiti
2023-03-22 13:38 ` Alexandre Ghiti
2023-05-09 19:07 ` Andreas Schwab
2023-05-09 19:55 ` Alexandre Ghiti
2023-05-11 18:18 ` Andreas Schwab
2023-05-12 18:41 ` Palmer Dabbelt [this message]
2023-05-19 11:08 ` Alexandre Ghiti
2023-05-19 21:48 ` Andreas Schwab
2023-05-19 21:55 ` Palmer Dabbelt
2023-05-22 10:48 ` Alexandre Ghiti
2023-02-15 14:36 ` [PATCH v8 2/3] powerpc: Move script to check relocations at compile time in scripts/ Alexandre Ghiti
2023-02-15 14:36 ` [PATCH v8 3/3] riscv: Check relocations at compile time Alexandre Ghiti
2023-02-20 9:14 ` [PATCH v8 0/3] Introduce 64b relocatable kernel Björn Töpel
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=mhng-c528747d-5f47-4e42-b6db-f9db4e756ff9@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=alex@ghiti.fr \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=schwab@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).