Kernel Panic: Oops - store (or AMO) access fault in __memset during gcc/gentoo-sources compilation on riscv64 (JH7110 / Star64)

[Vivian Wang]

On 5/18/26 11:25, Vivian Wang wrote:
> Hi Артем Макєєв,
>
> On 5/18/26 00:45, Артем Макєєв wrote:
>> [...]
> [...]
>
> It would also help if you could provide these information:
>
>   * Version information of U-Boot, OpenSBI, etc, as they would
>     self-report on serial port on boot.
>   * Full boot time kernel logs. It doesn't have to be all the way to the
>     panic; just up to a normal startup is enough.

I received private replies from Артем with logs that had confirmed my
diagnosis. I'm replying publicly for posterity.

On 5/18/26 15:21, Артем Макєєв wrote:

> [...]
>
> Opensbi and uboot version and log:

(I removed most of the logs to hide possibly private information.)

> [...]
>
> U-Boot 2021.10 (Jan 19 2023 - 04:09:41 +0800), Build: jenkins-github_visionfive2-6

This is StarFive's firmware. I would recommend replacing it with a newer
mainline U-Boot since StarFive's is quite an old version and has many
vendor-specific modifications that may not be unsuitable for a general
distro.

There is a very detailed guide in the U-Boot documentation:

    https://docs.u-boot.org/en/latest/board/starfive/pine64_star64.html

It is generally safe to do so, since the existence of the UART boot mode
means that it is not generally possible to brick a JH7110 board with bad
software. Do note that version 2025.10 onwards stopped supporting
firmware-on-SD-card boot so you would have to use an older version or
customize it somewhat if you're using that.

I don't know how your distro sets up the boot configuration to let
U-Boot find your kernel, etc, so I don't know if it's compatible with
the de facto standards that mainline U-Boot uses. If you're unfamiliar
with how to set up stuff like extlinux booting, it would be better to
ask other Gentoo users for help, since it's wildly different between
distros.

> [...]
>
> [    0.000000] Machine model: Pine64 Star64
> [    0.000000] SBI specification v1.0 detected
> [    0.000000] SBI implementation ID=0x1 Version=0x10002
> [    0.000000] SBI TIME extension detected
> [    0.000000] SBI IPI extension detected
> [    0.000000] SBI RFENCE extension detected
> [    0.000000] SBI SRST extension detected
> [    0.000000] efi: UEFI not found.
> [    0.000000] earlycon: uart0 at MMIO32 0x0000000010000000 (options '115200n8')
> [    0.000000] printk: legacy bootconsole [uart0] enabled
> [    0.000000] OF: reserved mem: Reserved memory: No reserved-memory node in the 
>
This means that it's definitely the firmware's problem, since there
definitely should be some reserved memory for OpenSBI, either from UEFI
(which does not apply here) or /reserved-memory (it's missing). Without
this information Linux could not know that some memory is not usable.

Vivian "dramforever" Wang