U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Alexander Feilke <Alexander.Feilke@ew.tq-group.com>
Cc: 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: Tue, 25 Nov 2025 10:35:24 -0600	[thread overview]
Message-ID: <20251125163524.GQ2125796@bill-the-cat> (raw)
In-Reply-To: <20251125161427.1155-1-Alexander.Feilke@ew.tq-group.com>

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

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
> ---
>  lib/fdtdec.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/fdtdec.c b/lib/fdtdec.c
> index c38738b48c7..0f2f7c948cd 100644
> --- a/lib/fdtdec.c
> +++ b/lib/fdtdec.c
> @@ -1257,7 +1257,7 @@ static void *fdt_find_separate(void)
>  	/* FDT is at end of image */
>  	fdt_blob = (ulong *)_end;
>  
> -	if (_DEBUG && !fdtdec_prepare_fdt(fdt_blob)) {
> +	if (1 && !fdtdec_prepare_fdt(fdt_blob)) {
>  		int stack_ptr;
>  		const void *top = fdt_blob + fdt_totalsize(fdt_blob);
>  

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

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

  reply	other threads:[~2025-11-25 16:35 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 [this message]
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
  -- 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=20251125163524.GQ2125796@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=Alexander.Feilke@ew.tq-group.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