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: Fabio Estevam <festevam@gmail.com>,
	Simon Glass <sjg@chromium.org>,
	u-boot@lists.denx.de, u-boot@ew.tq-group.com
Subject: Re: [BUG] silent hangup when debugging lib/fdtdec.c
Date: Thu, 15 Jan 2026 12:50:30 -0600	[thread overview]
Message-ID: <20260115185030.GH3416603@bill-the-cat> (raw)
In-Reply-To: <d6f95-69660800-e9-39c27bc0@93971335>

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

On Tue, Jan 13, 2026 at 09:52:35AM +0100, alexander.feilke@ew.tq-group.com wrote:
> > > 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?
> > >
> > 
> > I can boot and reproduce the hangup issue on mx7dsabresd:
> > 
> > <debug_uart>
> > FDT 8787da38 gd 0091de20
> > top 87887538 sp 87800000
> > sys_init_sp_addr 0091ff10
> > gbl_data_size 000000f0
> > FDT overlap
> > resetting ...
> > System reset not supported on this platform
> > ### ERROR ### Please RESET the board ###
> 
> Just want to revive this topic as the issue is still unresolved.

OK, so looking at this, it's a "feature" as the check doesn't take in to
account that we might not have relocated gd out of initial memory (in
this case, 0x009.....) and in to sdram (0x8.......) and so is a faulty
check.

-- 
Tom

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

  reply	other threads:[~2026-01-15 18:50 UTC|newest]

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

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=20260115185030.GH3416603@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