U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: "alexander.feilke@ew.tq-group.com" <alexander.feilke@ew.tq-group.com>
Cc: Simon Glass <sjg@chromium.org>,
	u-boot@lists.denx.de, u-boot@ew.tq-group.com,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: [BUG] silent hangup when debugging lib/fdtdec.c
Date: Wed, 26 Nov 2025 08:56:21 -0600	[thread overview]
Message-ID: <20251126145621.GS2125796@bill-the-cat> (raw)
In-Reply-To: <2db22e-6926d980-129-2e0bef80@48422766>

[-- Attachment #1: Type: text/plain, Size: 2593 bytes --]

On Wed, Nov 26, 2025 at 11:41:14AM +0100, alexander.feilke@ew.tq-group.com wrote:
> On Tuesday, November 25, 2025 17:35 CET, Tom Rini <trini@konsulko.com> wrote:
> 
> > On Tue, Nov 25, 2025 at 05:14:12PM +0100, Alexander Feilke wrote:
> > 
> > > From: Alexander Feilke <alexander.feilke@ew.tq-group.com>
> > > 
> > > Description: U-Boot hangs silently during boot when enabling DEBUG in
> > > lib/fdtdec.c
> > > 
> > > Not sure if its really a bug or rather a configuration issue on my side.
> > > 
> > > Minimal steps to reproduce: <see patch>
> > > 
> > > The hang is caused by `panic("FDT overlap");` later inside the if block.
> > > (see `lib/fdtdec.c:1279` in `fdt_find_separate(void)`)
> > > 
> > > Additionally, no boot log can be seen because serial is initialized after
> > > loading the devicetree in this boot stage (see `common/board_r.c:665` in
> > > `initcall_run_r(void)`)
> > > 
> > > Tested on i.MX6 with configs for tqma6d_mba6 and other tq boards that aren't,
> > > mainlined yet (tqma6ulx_mba6ul and tqma7d_mba7).
> > > 
> > > Any idea what to look for to fix this on our side?
> > > 
> > > Thanks in advance,
> > > Alexander
> > 
> > For very early failures you might need to look at enabling DEBUG_UART
> > which wires in a more direct "just write this to serial port".
> > 
> > -- 
> > Tom
> 
> Thanks for pointing that out. The debug log shows that the global data is
> still located in the SRAM after relocation.
> Printing all variables involved in the panic condition shows, that the stack
> pointer also overflowed, so there appear to be two separate issues.
> 
> if (top > (void *)gd || top > (void *)&stack_ptr) {
> 
> including top, sp and sys_init_sp_addr for completeness:
> 
> <debug_uart>
> FDT 8789d3a0 gd 0091de40
> top 878a7aa8 sp 878543e7
> sys_init_sp_addr 0091ff20
> FDT overlap
> resetting ...
> System reset not supported on this platform
> ### ERROR ### Please RESET the board ###
> 
> 
> Note: I don't use CUSTOM_SYS_INIT_SP_ADDR so the default is used. GENERATED_GBL_DATA_SIZE is 0xe0
> 
> #define SYS_INIT_SP_ADDR	(CFG_SYS_INIT_RAM_ADDR + CFG_SYS_INIT_RAM_SIZE
>  - GENERATED_GBL_DATA_SIZE)
> #define CFG_SYS_INIT_RAM_ADDR	IRAM_BASE_ADDR
> #define CFG_SYS_INIT_RAM_SIZE	IRAM_SIZE
> 
> Do you have any idea how to address these two problems?

Are there similar configs upstream? I know that imx6 is not generally
broken, I boot my mx6cuboxi on current next (and master recently) and
it's not failing like that, for example. Also, adding in one of the imx
custodians..

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-26 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 16:14 [BUG] silent hangup when debugging lib/fdtdec.c Alexander Feilke
2025-11-25 16:35 ` Tom Rini
2025-11-26 10:41   ` alexander.feilke
2025-11-26 14:56     ` Tom Rini [this message]
2025-11-27 12:32       ` alexander.feilke
2025-11-27 14:02         ` Fabio Estevam
  -- strict thread matches above, loose matches on Subject: below --
2025-11-27 15:50 alexander.feilke
2025-12-10  8:33 ` alexander.feilke
2026-01-13  8:52 ` alexander.feilke
2026-01-15 18:50   ` Tom Rini

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=20251126145621.GS2125796@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=alexander.feilke@ew.tq-group.com \
    --cc=festevam@gmail.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@ew.tq-group.com \
    --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