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 CAAC6C761AF for ; Wed, 5 Apr 2023 07:20:36 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 8AFF785C54; Wed, 5 Apr 2023 09:20:33 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmx.de Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; secure) header.d=gmx.de header.i=deffo@gmx.de header.b="b3QQbN+6"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 8E51585D37; Wed, 5 Apr 2023 09:20:31 +0200 (CEST) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id BD178859B4 for ; Wed, 5 Apr 2023 09:20:27 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmx.de Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=deffo@gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1680679226; i=deffo@gmx.de; bh=NgpwS2fbZqkAMBBptGsnhyU4zBDuTKEuJxh2edTrEiI=; h=X-UI-Sender-Class:From:To:Cc:Subject:Date; b=b3QQbN+6e+jPZM3BBY3nC00ERrm0bHWaF0OhHuC9CX3aeB+E8rgb1vHlGYtVP1zsM br+vfyd74V7YPONQWKQqeSsCrycHZZhVEQH42VlOKR5jUAa6z7FIH5azLYQCv12VZM V5uVrmX9LPr6qkHqj7Op3WNj/OzxdP0I/pcMbBt22j6BQxj4/81QSCgtneDqJPfGCx Z4yckoukKi8xcnl6ULHtuc799tkc9649ITA4bP6CQF2jG5yIo3KuKgTdKrnxMLS5Dm dafECWMvwi78Cjba3YbTfFefrnhx3vixRNtJrViSaTzCRJ1DtYx2KxJkqN31QQsP2N eOblzTlHTle7A== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from [46.5.1.147] ([46.5.1.147]) by web-mail.gmx.net (3c-app-gmx-bap55.server.lan [172.19.172.125]) (via HTTP); Wed, 5 Apr 2023 09:20:26 +0200 MIME-Version: 1.0 Message-ID: From: deffo@gmx.de To: sjg@chromium.org Cc: u-boot@lists.denx.de Subject: Re: Newer U-Boot version throwing "Bootstage space exhasuted" with FIT image Content-Type: text/plain; charset=UTF-8 Date: Wed, 5 Apr 2023 09:20:26 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:d7B7rlyXlvFcPxg48YYiLt+EirgvApxbsxmfxIFsZGTyrDYLSpjsStF6cbxZSRGkIrgXi QCWZHru52LXEW32MhCgI4WGOzodv07Dw5nFm4af+K+kMp1p9TfuLCPIpKFTdldV9ScTuMB+ZKs9J R9XyBVs8bF839ab6xS6DC99zMsZ4VNR/A1qanDVLcvfGUAj2XAvomHFJ+0HDwTHahdYaQVAP1FP2 jFm3ufKP4/RrehZZ+yGjDlM0SWF0GHm4NgDvJjcoQuVLY70ypLdf5yQppFUmn98F2yBHk12QfYlq E8= UI-OutboundReport: notjunk:1;M01:P0:YQf6Ohl/yxk=;UIZddtlni/2xuFtxNkd1mOXeZNQ CllONtMdEY2T/m7+AEc81aRVux1UbuYltnKK90gHcmGTkgGk9L3T6vTa7AWUgM8fbSfDTxP/S 7a8MtOh3lYhHSjsVBPWTksuRjuASyQDcaHNKqqsGlTlNwV6bmPFwSxymcaPXUDpAxnk5OOfSF ExY9LZEoUuoyIku9DUjKBRYE/HCfKNNuL1GPKSWlqj6AQv1FHiLpK0lfR/kWDjRpi9RQnGT4P u8prW+yGiMGzwCnR+Sj3tB66bmj6U+02nrXKLQRoyFbNuFNdtQ3imYSPXriE0P9gzmb0407wm AHXnS8PDw1GzrMdgNb5ettOvvm7RiP2t99eRjbe1EwIKl5GypFQUjhiXNl+/fJFC0AThi7a4J t0xwwsLUJnK3xo1FuKs33fGhCdnh+L8xeIbhTL05yQ2v2uZmba/uPAsF5Bw4E64MC81eCzS74 nm7uHY1D6DPREHll232DSab79gNEyL7dDjcnNsmpwLBU/h+aDyVEpCtHXM6LSsJIasAtBdCKy OgCSyPV2jd9gRlUpxxAq5uyHC8AjjZztb8yMTBJBVZhrCw80Esti9gOKrioehNzfh9EzHaNtB 1HWr8tDn84ENv/fjL9K371n3lnbNjq6sr1Xao4jm6ZHO35Yu88C9g3Bd/MKvvIWy5Xk8O8HjO FPKzh7zsZsNBMmlR9aopaTTWMVf9EjOAABvPnqD3q3/AvPhj4eDZnbKCn4lWK4u3QPpC+uQ9f K1S4bUvwALhIqeAL1mIVzDyDxR6C9OrxzV3gh4rOL2TQd+C1d3xEdkv28mAhcZqBc9yIcPL4/ K9DJ/3oMX28OgBjQ1ZC7o/mA== Content-Transfer-Encoding: quoted-printable 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 Simon, even with CONFIG_BOOTSTAGE disabled I still get this data abort: Starting kernel ... data abort pc : [] lr : [<00000000>] reloc pc : [] lr : [] sp : fbbefafc ip : 00000000 fp : 00000001 r10: c20000d8 r9 : fbbffec0 r8 : 00000000 r7 : 00000000 r6 : 00000000 r5 : e28ff010 r4 : 00000000 r3 : 00000000 r2 : 00000a10 r1 : fdfab018 r0 : 2ffc0020 Flags: nzCv IRQs off FIQs off Mode SVC_32 (T) Code: f891 f03c f891 f05c (f891) f07c Resetting CPU ... resetting ... How can I debug this any further? Best regards =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 i= s active: > > STM32MP> bdinfo > boot_params =3D 0x00000000 > DRAM bank =3D 0x00000000 > -> start =3D 0xc0000000 > -> size =3D 0x40000000 > flashstart =3D 0x00000000 > flashsize =3D 0x00000000 > flashoffset =3D 0x00000000 > baudrate =3D 115200 bps > relocaddr =3D 0xfdf3a000 > reloc off =3D 0x3de3a000 > Build =3D 32-bit > current eth =3D ethernet@5800a000 > ethaddr =3D 00:00:00:00:00:00 > IP addr =3D > fdt_blob =3D 0xfbf27e10 > new_fdt =3D 0xfbf27e10 > fdt_size =3D 0x000100a0 > lmb_dump_all: > memory.cnt =3D 0x1 > memory[0] [0xc0000000-0xffffffff], 0x40000000 bytes flags: 0 > reserved.cnt =3D 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 =3D board > arch_number =3D 0x00000000 > TLB addr =3D 0xfdff0000 > irq_sp =3D 0xfbf27b80 > sp start =3D 0xfbf27b70 > Early malloc usage: 11f8 / 3000 > STM32MP> ext4load mmc ${boot_instance}:${boot_part} ${kernel_addr_r} ${l= inux}; 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 =3D 7.2 MiB > Architecture: ARM > OS: Linux > Load Address: 0xc0008000 > Entry Point: 0xc0008000 > Hash algo: sha256 > Hash value: b0ca7e8de523721697b6990e67f142159845f1b5e2a52a4fef4da= 8f6754d49a7 > Sign algo: sha256,rsa2048:board > Sign value: unavailable > Timestamp: unavailable > Verifying Hash Integrity ... sha256+ OK > kernel data at 0xc20000d8, len =3D 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 =3D 2.9 MiB > Architecture: ARM > OS: Linux > Load Address: unavailable > Entry Point: unavailable > Hash algo: sha256 > Hash value: 3d9201eee8e91a161719ea35b630d9d09dc6be204fcda3390ecd7= a540e322048 > 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 =3D 60.9 KiB > Architecture: ARM > Load Address: 0xc4000000 > Hash algo: sha256 > Hash value: 2b1df931402fd642c8a1618aa140630e22fed4c095deed4df2016= 37f008630ea > 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 =3D 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 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 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 "Boo= tstage 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 =3D 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 t= race. 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 b= oots. Regards, Simon