u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: deffo@gmx.de
To: u-boot@lists.denx.de
Subject: Newer U-Boot version throwing "Bootstage space exhasuted" with FIT image
Date: Fri, 31 Mar 2023 15:38:21 +0200	[thread overview]
Message-ID: <trinity-7c931659-d2e7-4e51-bbe9-cd764cee2f64-1680269901448@3c-app-gmx-bap23> (raw)

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 ...

             reply	other threads:[~2023-03-31 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 13:38 deffo [this message]
2023-04-01  6:32 ` Newer U-Boot version throwing "Bootstage space exhasuted" with FIT image Simon Glass
2023-04-02 12:43 deffo
2023-04-02 18:45 ` Simon Glass
2023-04-05  7:20 deffo
2023-04-05 18:37 ` Simon Glass

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=trinity-7c931659-d2e7-4e51-bbe9-cd764cee2f64-1680269901448@3c-app-gmx-bap23 \
    --to=deffo@gmx.de \
    --cc=u-boot@lists.denx.de \
    /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).