Re: Radxa Orion O6

From: Andrew Turner <andrew_at_fubar.geek.nz>
Date: Wed, 22 Jan 2025 11:58:07 UTC 
On 2025-01-22 05:47, FUKAUMI Naoki wrote:
...
> ram0: reserving memory region:   84400000-84600000
> ram0: reserving memory region:   85000000-a0000000
> panic: ram_attach: resource 1 failed to attach
> cpuid = 0
> time = 1
> KDB: stack backtrace:
> db_trace_self() at db_trace_self
> db_trace_self_wrapper() at db_trace_self_wrapper+0x38
> vpanic() at vpanic+0x1a0
> panic() at panic+0x48
> ram_attach() at ram_attach+0xec
> device_attach() at device_attach+0x4c0
> bus_generic_new_pass() at bus_generic_new_pass+0x130
> bus_generic_new_pass() at bus_generic_new_pass+0xc0
> root_bus_configure() at root_bus_configure+0x44
> mi_startup() at mi_startup+0x1f4
> virtdone() at virtdone+0x6c
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at      kdb_enter+0x48: str     xzr, [x19, #2048]
> db>

As a workaround you can disable the ram0 device by exiting to the loader 
prompt and running the following:

set hint.ram.0.disabled=1
boot

We may find something has reserved the memory that will attach after the 
ram0 device.

Andrew