SpacemiT k1: Linux crashes setting up smp with mainline U-Boot

Junhui Liu junhui.liu at pigmoral.tech
Thu Dec 11 17:50:53 PST 2025


Hi Michael,

On 12/12/25 4:34 AM, Michael Opdenacker wrote:
[...]
> [   0.000000] SBI specification v3.0 detected
> [    0.000000] SBI implementation ID=0x1 Version=0x10007
> [    0.000000] SBI TIME extension detected
> [    0.000000] SBI IPI extension detected
> [    0.000000] SBI RFENCE extension detected
> [    0.000000] SBI DBCN extension detected
> [    0.000000] SBI FWFT extension detected
>
[...]
> syys 0.083956] smp: Bringing upsysysys: sys: 0xss
> 1.  sys:t:: r  y00 xxs01fxdcfe121.0
> 210c.
>
>   b0
> m:3
> j...

This might actually not a "crash". Instead, it seems the boot address for
CPUs 1-7 hasn't been set correctly, causing them to boot from the BootROM.

I believe this is not a U-Boot issue, but rather an OpenSBI one. According
to the log, it looks like you are using mainline OpenSBI. Could you please
confirm the OpenSBI you are using includes this fix:

126c9d34 ("platform: generic: spacemit: add missing objects.mk")

-- 
Best regards,
Junhui Liu




More information about the linux-riscv mailing list