Hi,

On Sat, 1 Apr 2023 at 02:57, deffo@gmx.de wrote:

Hi,

I changed from v2020.10 to v2022.10 and suddenly I get a bunch of "Bootstage space exhasuted" messages during bootm.

reloc pc : [<c01018ba>] is memcpy()

It evens triggers a reset. Older version works just fine:

 Sign value:   unavailable
 Timestamp:    unavailable

Verifying Hash Integrity ... sha256+ OK Bootstage space exhasuted Bootstage space exhasuted Bootstage space exhasuted Bootstage space exhasuted Loading fdt from 0xc272de94 to 0xc4000000 Bootstage space exhasuted Booting using the fdt blob at 0xc4000000 Loading Kernel Image kernel loaded at 0xc0008000, end = 0xc0735c80 Bootstage space exhasuted Bootstage space exhasuted Loading Ramdisk to cfd23000, end cffff105 ... OK Loading Device Tree to cfd10000, end cfd22375 ... OK Bootstage space exhasuted Bootstage space exhasuted

Starting kernel ...

data abort pc : [<fdf3b8ba>] lr : [<00000000>] reloc pc : [<c01018ba>] lr : [<c21c6000>] sp : fbf2786c ip : 00000000 fp : 00000001 r10: c20000d8 r9 : fbf37eb0 r8 : 00000000 r7 : 00000000 r6 : 00000000 r5 : e28ff010 r4 : 00000000 r3 : 00000000 r2 : 00000a10 r1 : fdfabb14 r0 : 2ffc0020 Flags: nzCv IRQs off FIQs off Mode SVC_32 (T) Code: f891 f03c f891 f05c (f891) f07c Resetting CPU ...

resetting ...

Do you know which board it is? It would help to produce a full console trace.

Regards, Simon