From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C50C6C7619A for ; Sun, 2 Apr 2023 18:45:25 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id B577185ABA; Sun, 2 Apr 2023 20:45:22 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=chromium.org header.i=@chromium.org header.b="BII55mm/"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 94DED85C5F; Sun, 2 Apr 2023 20:45:20 +0200 (CEST) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 707B785A1D for ; Sun, 2 Apr 2023 20:45:16 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=sjg@google.com Received: by mail-ed1-x536.google.com with SMTP id r11so109067967edd.5 for ; Sun, 02 Apr 2023 11:45:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1680461116; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=gXjxJzuEgSaC6tVniCVtU9yDZ/gOy/xNAG9Imn/iPPA=; b=BII55mm/BMgPae9caAjE6YkSM4id20i47WtLHEIomjVGFAlllFNWiYmJPdeJyhcTY9 iw3+II5NfX5ls0P7957v5MYpGubJzYTOLJFjShUqzQ6BSm6Yh+VqOIJFo0NmdjsTZItH IEPmfL9RPIahM6LmxvDzfAroxRGjXIr+33UrM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680461116; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gXjxJzuEgSaC6tVniCVtU9yDZ/gOy/xNAG9Imn/iPPA=; b=11VnQU5bz/Z6Gcr+w953R5B0rEh1TGcsvmUGgnP5aJq+BmGGOFL20Ig4AGMmsZCcRG iRiWtx1n7TpABFUsbQp27DHN6XmxWC2Kwr8RExKwEcEmTIypnJttQ/ZSQVb8DjDJ6/cJ Sar1Zf3aDxjjpcAtN5aXGIkDcQ9Pvhi6i+86B5NknJYtBuCmpASDVYJczh/wpJaPHvpU cY0tF4GVKmXKLxHH0wN19TfiFHHj4Au2xrpZgigKJmG2tE+gQs1LpJKVvX2toWKXQSlp VEcsau/nCnZyk7F+rQ1MdN4kaGK2XMGYytehAbyHTKdfw1qPPWebOTxfOs4CTdcwT22Q z74A== X-Gm-Message-State: AAQBX9fWwymJ/pSbWXL+1NCYLza9wx/ldqGsJK6tti7ffWLQ43/2fB0L /hbzPqUJrl/6REcmLZLHoOd3EErMSK/MAhopiQiJWJxZqaol6Lv8Mpg= X-Google-Smtp-Source: AKy350agpMN4LLyLbUF7HEJpxJ8FQlQ0FldYWR8zldy6lA0R2diKshAacotrE8XASG1iymyVM6rZqvM6D0f4ARCRlrw= X-Received: by 2002:a17:906:b884:b0:932:a33a:3754 with SMTP id hb4-20020a170906b88400b00932a33a3754mr16495879ejb.14.1680461115590; Sun, 02 Apr 2023 11:45:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Simon Glass Date: Mon, 3 Apr 2023 06:45:03 +1200 Message-ID: Subject: Re: Newer U-Boot version throwing "Bootstage space exhasuted" with FIT image To: deffo@gmx.de Cc: u-boot@lists.denx.de Content-Type: text/plain; charset="UTF-8" X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean Hi, On Mon, 3 Apr 2023 at 00:43, wrote: > > Hi Simon, > > it's an STM32MP1, here's a bdinfo and the full boot log. Btw, OPTEE OS is active: > > STM32MP> bdinfo > boot_params = 0x00000000 > DRAM bank = 0x00000000 > -> start = 0xc0000000 > -> size = 0x40000000 > flashstart = 0x00000000 > flashsize = 0x00000000 > flashoffset = 0x00000000 > baudrate = 115200 bps > relocaddr = 0xfdf3a000 > reloc off = 0x3de3a000 > Build = 32-bit > current eth = ethernet@5800a000 > ethaddr = 00:00:00:00:00:00 > IP addr = > fdt_blob = 0xfbf27e10 > new_fdt = 0xfbf27e10 > fdt_size = 0x000100a0 > lmb_dump_all: > memory.cnt = 0x1 > memory[0] [0xc0000000-0xffffffff], 0x40000000 bytes flags: 0 > reserved.cnt = 0x5 > reserved[0] [0x10000000-0x10047fff], 0x00048000 bytes flags: 4 > reserved[1] [0x30000000-0x3003ffff], 0x00040000 bytes flags: 4 > reserved[2] [0x38000000-0x3800ffff], 0x00010000 bytes flags: 4 > reserved[3] [0xfbf23940-0xfdffffff], 0x020dc6c0 bytes flags: 0 > reserved[4] [0xfe000000-0xffffffff], 0x02000000 bytes flags: 4 > devicetree = board > arch_number = 0x00000000 > TLB addr = 0xfdff0000 > irq_sp = 0xfbf27b80 > sp start = 0xfbf27b70 > Early malloc usage: 11f8 / 3000 > STM32MP> ext4load mmc ${boot_instance}:${boot_part} ${kernel_addr_r} ${linux}; bootm ${kernel_addr_r} > 10590706 bytes read in 542 ms (18.6 MiB/s) > ## Loading kernel from FIT Image at c2000000 ... > Using 'config' configuration > Trying 'kernel' kernel subimage > Description: Linux kernel - base > Created: 2023-03-31 12:45:20 UTC > Type: Kernel Image > Compression: uncompressed > Data Start: 0xc20000d8 > Data Size: 7527552 Bytes = 7.2 MiB > Architecture: ARM > OS: Linux > Load Address: 0xc0008000 > Entry Point: 0xc0008000 > Hash algo: sha256 > Hash value: b0ca7e8de523721697b6990e67f142159845f1b5e2a52a4fef4da8f6754d49a7 > Sign algo: sha256,rsa2048:board > Sign value: unavailable > Timestamp: unavailable > Verifying Hash Integrity ... sha256+ OK > kernel data at 0xc20000d8, len = 0x0072dc80 (7527552) > ## Loading ramdisk from FIT Image at c2000000 ... > Using 'config' configuration > Trying 'ramdisk' ramdisk subimage > Description: ramdisk > Created: 2023-03-31 12:45:20 UTC > Type: RAMDisk Image > Compression: uncompressed > Data Start: 0xc273d318 > Data Size: 2998533 Bytes = 2.9 MiB > Architecture: ARM > OS: Linux > Load Address: unavailable > Entry Point: unavailable > Hash algo: sha256 > Hash value: 3d9201eee8e91a161719ea35b630d9d09dc6be204fcda3390ecd7a540e322048 > Sign algo: sha256,rsa2048:board > Sign value: unavailable > Timestamp: unavailable > Verifying Hash Integrity ... sha256+ OK > ## Loading fdt from FIT Image at c2000000 ... > Bootstage space exhasuted > Using 'config' configuration > Trying 'dtb' fdt subimage > Description: DeviceTree blob - base > Created: 2023-03-31 12:45:20 UTC > Type: Flat Device Tree > Compression: uncompressed > Data Start: 0xc272de94 > Data Size: 62326 Bytes = 60.9 KiB > Architecture: ARM > Load Address: 0xc4000000 > Hash algo: sha256 > Hash value: 2b1df931402fd642c8a1618aa140630e22fed4c095deed4df201637f008630ea > Sign algo: sha256,rsa2048:board > 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 : [] lr : [<00000000>] > reloc pc : [] lr : [] > 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 ... > > Thanks and best regards > > ====================================== > > Hi, > > On Sat, 1 Apr 2023 at 02:57, 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 : [] 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 : [] lr : [<00000000>] > > reloc pc : [] lr : [] > > 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. If you disabled CONFIG_BOOTSTAGE does the problem go away? Running out of space should not cause any problems. Also, try disabling CONFIG_BOOTSTAGE and see if that makes a difference. You can enable CONFIG_BOOTSTAGE_REPORT to see a report before the kernel boots. Regards, Simon