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 3C133C5479D for ; Thu, 12 Jan 2023 00:10:27 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 51A4485345; Thu, 12 Jan 2023 01:10:25 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=konsulko.com 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=konsulko.com header.i=@konsulko.com header.b="HjikT0BL"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 8680F85345; Thu, 12 Jan 2023 01:10:23 +0100 (CET) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 C9E5A8500A for ; Thu, 12 Jan 2023 01:10:18 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=konsulko.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=trini@konsulko.com Received: by mail-qt1-x836.google.com with SMTP id j15so9768869qtv.4 for ; Wed, 11 Jan 2023 16:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsulko.com; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=KzLrYhGIr7Xvn7WUgpTtjF2LhGb5p5HZKm1BmQICDn0=; b=HjikT0BL+Mf5uWZg6JziTYFWmNpOL6CZKrjF9BYJPTXYK7cOQLXYKkHQSabWcEbhBx qmZR6GsUCXh+e+GkBy3rBOmQ2x9zl/JZ/CyVzqAM78GzRlX18Z0q9dMFQs3R+fiu5vsF 6Faks0IU+CjW2hP2bGLi1sECzFRd3bfm/IZlA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=KzLrYhGIr7Xvn7WUgpTtjF2LhGb5p5HZKm1BmQICDn0=; b=d8RjTpFkBqZTILMEAgDuy8S8IEB80LpNss5JnPem/mnFU0KGeuLRyccgz3bdJx8bpB 4GGeJB8HLFVrDNkUekNPdhXmxadVWtPoLV6XxR/UNKhKt/DHbR6f/sJ/0KkFWg4Pdlvk uSqcYXYakvBNZziE1AK6BQX/o55KNoFMlwgE+cbk8Nu7Gt/OVhzLc/5Gi/AdYcewoYz4 0CtJoo4Os0rFCbOn+j5kOK/Dt64fX8hI6oTskDLlxhKCufR/X+bHDazce7k2xTHkLN+F wDe2ckaKvO/JEPTMB1tD2l34BwJJPs4MeRGpnhP8O16LpfNZ7OfA9YRyq1piK1rcB9Lg cEog== X-Gm-Message-State: AFqh2kpzT4nId62hbvyPqwgV4otvW9saKwSomWpNw1GYicFHBo1JERkx iMdC2AwgDwBghX3QvbYChuogNg== X-Google-Smtp-Source: AMrXdXuPQo4VgyzyAKwRX67Ek2asJ8XPR8n3BzpMRcZEWVeAO7oSsyN/y54NYa5BssmsrcaIov167w== X-Received: by 2002:ac8:71c8:0:b0:3a9:8298:9969 with SMTP id i8-20020ac871c8000000b003a982989969mr13456604qtp.22.1673482217466; Wed, 11 Jan 2023 16:10:17 -0800 (PST) Received: from bill-the-cat (2603-6081-7b00-6400-6c6c-38e9-6d60-4422.res6.spectrum.com. [2603:6081:7b00:6400:6c6c:38e9:6d60:4422]) by smtp.gmail.com with ESMTPSA id h6-20020ac81386000000b003a7fef41526sm8210338qtj.77.2023.01.11.16.10.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 11 Jan 2023 16:10:16 -0800 (PST) Date: Wed, 11 Jan 2023 19:10:15 -0500 From: Tom Rini To: Joost van Zwieten Cc: Jaehoon Chung , u-boot@lists.denx.de Subject: Re: kernel doesn't start on Odroid U2 unless setting initrd_high Message-ID: <20230112001015.GR3787616@bill-the-cat> References: <20230110184101.GO3787616@bill-the-cat> <20230110230824.GR3787616@bill-the-cat> <20230110232915.GS3787616@bill-the-cat> <20230111203844.GO3787616@bill-the-cat> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="WPoY8ImOH9Y1oC7/" Content-Disposition: inline In-Reply-To: X-Clacks-Overhead: GNU Terry Pratchett 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.6 at phobos.denx.de X-Virus-Status: Clean --WPoY8ImOH9Y1oC7/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 11, 2023 at 10:08:59PM +0100, Joost van Zwieten wrote: >=20 >=20 > On Wed, Jan 11, 2023 at 15:38, Tom Rini wrote: > > On Wed, Jan 11, 2023 at 09:28:42PM +0100, Joost van Zwieten wrote: > > >=20 > > >=20 > > > On Tue, Jan 10, 2023 at 18:29, Tom Rini wrote: > > > > On Wed, Jan 11, 2023 at 12:10:42AM +0100, Joost van Zwieten wrote: > > > > > > > > > > > > > > > On Tue, Jan 10, 2023 at 18:08, Tom Rini > > > wrote: > > > > > > On Wed, Jan 11, 2023 at 12:01:46AM +0100, Joost van Zwieten > > > wrote: > > > > > > > > > > > > > > > > > > > > > On Tue, Jan 10, 2023 at 13:41, Tom Rini > > > > > > > > wrote: > > > > > > > > On Tue, Jan 10, 2023 at 09:13:32AM +0100, Joost van > > > Zwieten > > > > > wrote: > > > > > > > > > > > > > > > > > Dear maintainers, > > > > > > > > > > > > > > > > > > As of commit 4963f63fe61f15329d77472a762b1d8bf754d24b > > > > > U-Boot > > > > > > > fails > > > > > > > > > to start > > > > > > > > > a kernel (with `bootz`) on my Odroid U2 unless I > > > force > > > > > > > > > `initrd_high`, e.g. > > > > > > > > > to `0x50000000`. With commit 4963f63f and > > > `initrd_high` > > > > > > > *unset* I > > > > > > > > > get the > > > > > > > > > following output: > > > > > > > > > > > > > > > > > > U-Boot 2020.10-rc2-00314-g4963f63fe6 (Jan 09 2023 > > > - > > > > > 23:59:31 > > > > > > > > > +0100) > > > > > > > > > > > > > > > > > > CPU: Exynos4412 @ 1 GHz > > > > > > > > > Model: Odroid based on Exynos4412 > > > > > > > > > Type: u3 > > > > > > > > > DRAM: 2 GiB > > > > > > > > > LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling > > > > > > > > > LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling > > > > > > > > > LDO21@TFLASH_2.8V: set 2800000 uV; enabling > > > > > > > > > MMC: SAMSUNG SDHCI: 2, EXYNOS DWMMC: 0 > > > > > > > > > Loading Environment from MMC... *** Warning - bad > > > CRC, > > > > > using > > > > > > > > > default > > > > > > > > > environment > > > > > > > > > > > > > > > > > > In: serial > > > > > > > > > Out: serial > > > > > > > > > Err: serial > > > > > > > > > Boot device: MMC(2) > > > > > > > > > Net: No ethernet found. > > > > > > > > > Hit any key to stop autoboot: 0 > > > > > > > > > Odroid # env set fk_kvers 5.10.0-20-armmp > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > ${fdt_addr_r} > > > > > > > > > /boot/dtbs/${fk_kvers}/exynos4412-odroidu3.dtb > > > > > > > > > 53440 bytes read in 50 ms (1 MiB/s) > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > > > ${kernel_addr_r} > > > > > > > > > /boot/vmlinuz-${fk_kvers} > > > > > > > > > 4973056 bytes read in 182 ms (26.1 MiB/s) > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > > > ${ramdisk_addr_r} > > > > > > > > > /boot/initrd.img-${fk_kvers} > > > > > > > > > 22231585 bytes read in 777 ms (27.3 MiB/s) > > > > > > > > > Odroid # env set bootargs console=3DttySAC1,115200= n8 > > > > > > > > > Odroid # bootz ${kernel_addr_r} > > > > > > > ${ramdisk_addr_r}:${filesize} > > > > > > > > > ${fdt_addr_r} > > > > > > > > > Kernel image @ 0x41000000 [ 0x000000 - 0x4be200 ] > > > > > > > > > ## Flattened Device Tree blob at 40800000 > > > > > > > > > Booting using the fdt blob at 0x40800000 > > > > > > > > > Loading Ramdisk to b9947000, end bae7aa21 ... > > > OK > > > > > > > > > Loading Device Tree to b9936000, end b99460bf > > > ... OK > > > > > > > > > > > > > > > > > > Starting kernel ... > > > > > > > > > > > > > > > > > > And that's all I ever see. Normally the initrd loads > > > a > > > > > module > > > > > > > that > > > > > > > > > causes an > > > > > > > > > LED on the Odroid to blink, and this is not happening > > > > > either, > > > > > > > so > > > > > > > > > I'm pretty > > > > > > > > > confident the kernel doesn't start or at least > > > crashes > > > > > before > > > > > > > > > producing > > > > > > > > > output. If I set `initrd_high` to `0x50000000` (or > > > > > something > > > > > > > in the > > > > > > > > > neighborhood) the kernel starts just fine: > > > > > > > > > > > > > > > > > > U-Boot 2020.10-rc2-00314-g4963f63fe6 (Jan 09 2023 > > > - > > > > > 23:59:31 > > > > > > > > > +0100) > > > > > > > > > > > > > > > > > > CPU: Exynos4412 @ 1 GHz > > > > > > > > > Model: Odroid based on Exynos4412 > > > > > > > > > Type: u3 > > > > > > > > > DRAM: 2 GiB > > > > > > > > > LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling > > > > > > > > > LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling > > > > > > > > > LDO21@TFLASH_2.8V: set 2800000 uV; enabling > > > > > > > > > MMC: SAMSUNG SDHCI: 2, EXYNOS DWMMC: 0 > > > > > > > > > Loading Environment from MMC... *** Warning - bad > > > CRC, > > > > > using > > > > > > > > > default > > > > > > > > > environment > > > > > > > > > > > > > > > > > > In: serial > > > > > > > > > Out: serial > > > > > > > > > Err: serial > > > > > > > > > Boot device: MMC(2) > > > > > > > > > Net: No ethernet found. > > > > > > > > > Hit any key to stop autoboot: 0 > > > > > > > > > Odroid # env set fk_kvers 5.10.0-20-armmp > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > ${fdt_addr_r} > > > > > > > > > /boot/dtbs/${fk_kvers}/exynos4412-odroidu3.dtb > > > > > > > > > 53440 bytes read in 49 ms (1 MiB/s) > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > > > ${kernel_addr_r} > > > > > > > > > /boot/vmlinuz-${fk_kvers} > > > > > > > > > 4973056 bytes read in 181 ms (26.2 MiB/s) > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > > > ${ramdisk_addr_r} > > > > > > > > > /boot/initrd.img-${fk_kvers} > > > > > > > > > 22231585 bytes read in 777 ms (27.3 MiB/s) > > > > > > > > > Odroid # env set bootargs console=3DttySAC1,115200= n8 > > > > > > > > > Odroid # env set initrd_high 0x50000000 > > > > > > > > > Odroid # bootz ${kernel_addr_r} > > > > > > > ${ramdisk_addr_r}:${filesize} > > > > > > > > > ${fdt_addr_r} > > > > > > > > > Kernel image @ 0x41000000 [ 0x000000 - 0x4be200 ] > > > > > > > > > ## Flattened Device Tree blob at 40800000 > > > > > > > > > Booting using the fdt blob at 0x40800000 > > > > > > > > > Loading Ramdisk to 4eacc000, end 4ffffa21 ... > > > OK > > > > > > > > > Loading Device Tree to bae6a000, end bae7a0bf > > > ... OK > > > > > > > > > > > > > > > > > > Starting kernel ... > > > > > > > > > > > > > > > > > > [ 0.000000] Booting Linux on physical CPU 0xa00 > > > > > > > > > > > > > > > > > > > > > > > > > > > The difference between those two runs is the location > > > > > where > > > > > > > U-Boot > > > > > > > > > loads the > > > > > > > > > initrd. The parent commit of 4963f63f boots fine > > > without > > > > > > > setting > > > > > > > > > `initrd_high`: > > > > > > > > > > > > > > > > > > U-Boot 2020.10-rc2-00313-gdfaf6a5797 (Jan 10 2023 > > > - > > > > > 00:13:19 > > > > > > > > > +0100) > > > > > > > > > > > > > > > > > > CPU: Exynos4412 @ 1 GHz > > > > > > > > > Model: Odroid based on Exynos4412 > > > > > > > > > Type: u3 > > > > > > > > > DRAM: 2 GiB > > > > > > > > > LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling > > > > > > > > > LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling > > > > > > > > > LDO21@TFLASH_2.8V: set 2800000 uV; enabling > > > > > > > > > MMC: SAMSUNG SDHCI: 2, EXYNOS DWMMC: 0 > > > > > > > > > Loading Environment from MMC... *** Warning - bad > > > CRC, > > > > > using > > > > > > > > > default > > > > > > > > > environment > > > > > > > > > > > > > > > > > > In: serial > > > > > > > > > Out: serial > > > > > > > > > Err: serial > > > > > > > > > Boot device: MMC(2) > > > > > > > > > Net: No ethernet found. > > > > > > > > > Hit any key to stop autoboot: 0 > > > > > > > > > Odroid # env set fk_kvers 5.10.0-20-armmp > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > ${fdt_addr_r} > > > > > > > > > /boot/dtbs/${fk_kvers}/exynos4412-odroidu3.dtb > > > > > > > > > 53440 bytes read in 49 ms (1 MiB/s) > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > > > ${kernel_addr_r} > > > > > > > > > /boot/vmlinuz-${fk_kvers} > > > > > > > > > 4973056 bytes read in 181 ms (26.2 MiB/s) > > > > > > > > > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} > > > > > > > ${ramdisk_addr_r} > > > > > > > > > /boot/initrd.img-${fk_kvers} > > > > > > > > > 22231585 bytes read in 776 ms (27.3 MiB/s) > > > > > > > > > Odroid # env set bootargs console=3DttySAC1,115200= n8 > > > > > > > > > Odroid # bootz ${kernel_addr_r} > > > > > > > ${ramdisk_addr_r}:${filesize} > > > > > > > > > ${fdt_addr_r} > > > > > > > > > Kernel image @ 0x41000000 [ 0x000000 - 0x4be200 ] > > > > > > > > > ## Flattened Device Tree blob at 40800000 > > > > > > > > > Booting using the fdt blob at 0x40800000 > > > > > > > > > Loading Ramdisk to 4eacc000, end 4ffffa21 ... > > > OK > > > > > > > > > Loading Device Tree to 4eabb000, end 4eacb0bf > > > ... OK > > > > > > > > > > > > > > > > > > Starting kernel ... > > > > > > > > > > > > > > > > > > [ 0.000000] Booting Linux on physical CPU 0xa00 > > > > > > > > > > > > > > > > > > > > > > > > > > > I've tested two different kernels from Debian > > > (buster and > > > > > > > bullseye) > > > > > > > > > and both > > > > > > > > > have the same problem. I'm building U-Boot using the > > > > > default > > > > > > > config > > > > > > > > > for > > > > > > > > > board `odroid` and boot the Odroid from an SD card > > > with > > > > > > > firmware > > > > > > > > > (`bl1`, > > > > > > > > > `bl2` and `tzsw`) from Hardkernel's clone of the > > > u-boot > > > > > > > repository > > > > > > > > > [1]. > > > > > > > > > There are no peripherals connected apart from the SD > > > card > > > > > and > > > > > > > the > > > > > > > > > serial > > > > > > > > > console. Please let me know if you need more > > > information. > > > > > > > > > > > > > > > > Interesting. So what does "bdi" show, both in the older > > > good > > > > > and > > > > > > > > then current tree? Specifically the information about > > > where > > > > > DRAM > > > > > > > is, and > > > > > > > > how large it is? Thanks. > > > > > > > > > > > > > > > > -- > > > > > > > > Tom > > > > > > > > > > > > > > Both 4963f63f (not working) and its parent (working) > > > produce > > > > > the > > > > > > > same > > > > > > > output: > > > > > > > > > > > > > > boot_params =3D 0x40000100 > > > > > > > DRAM bank =3D 0x00000000 > > > > > > > -> start =3D 0x40000000 > > > > > > > -> size =3D 0x10000000 > > > > > > > DRAM bank =3D 0x00000001 > > > > > > > -> start =3D 0x50000000 > > > > > > > -> size =3D 0x10000000 > > > > > > > DRAM bank =3D 0x00000002 > > > > > > > -> start =3D 0x60000000 > > > > > > > -> size =3D 0x10000000 > > > > > > > DRAM bank =3D 0x00000003 > > > > > > > -> start =3D 0x70000000 > > > > > > > -> size =3D 0x10000000 > > > > > > > DRAM bank =3D 0x00000004 > > > > > > > -> start =3D 0x80000000 > > > > > > > -> size =3D 0x10000000 > > > > > > > DRAM bank =3D 0x00000005 > > > > > > > -> start =3D 0x90000000 > > > > > > > -> size =3D 0x10000000 > > > > > > > DRAM bank =3D 0x00000006 > > > > > > > -> start =3D 0xa0000000 > > > > > > > -> size =3D 0x10000000 > > > > > > > DRAM bank =3D 0x00000007 > > > > > > > -> start =3D 0xb0000000 > > > > > > > -> size =3D 0x0ff00000 > > > > > > > memstart =3D 0x40000000 > > > > > > > memsize =3D 0x7ff00000 > > > > > > > flashstart =3D 0x00000000 > > > > > > > flashsize =3D 0x00000000 > > > > > > > flashoffset =3D 0x00000000 > > > > > > > baudrate =3D 115200 bps > > > > > > > relocaddr =3D 0xbfe83000 > > > > > > > reloc off =3D 0x7c083000 > > > > > > > Build =3D 32-bit > > > > > > > current eth =3D unknown > > > > > > > ethaddr =3D (not set) > > > > > > > IP addr =3D > > > > > > > fdt_blob =3D 0xbae7bf00 > > > > > > > new_fdt =3D 0xbae7bf00 > > > > > > > fdt_size =3D 0x00002fa0 > > > > > > > lmb_dump_all: > > > > > > > memory.cnt =3D 0x1 > > > > > > > memory.size =3D 0x0 > > > > > > > memory.reg[0x0].base =3D 0x40000000 > > > > > > > .size =3D 0x7ff00000 > > > > > > > > > > > > > > reserved.cnt =3D 0x1 > > > > > > > reserved.size =3D 0x0 > > > > > > > reserved.reg[0x0].base =3D 0xbae7acd0 > > > > > > > .size =3D 0x5085330 > > > > > > > arch_number =3D 0x000010c1 > > > > > > > TLB addr =3D 0xbfef0000 > > > > > > > irq_sp =3D 0xbae7bef0 > > > > > > > sp start =3D 0xbae7bee0 > > > > > > > Board Type =3D 0 > > > > > > > Early malloc usage: f0 / 400 > > > > > > > > > > > > > > I'm not sure if this is relevant, but with the failing > > > commit > > > > > I can > > > > > > > get the > > > > > > > kernel to start with `initrd_high` set to `0x70000000` or > > > > > lower, > > > > > > > but not > > > > > > > higher. > > > > > > > > > > > > OK, so 8 whole banks, of 256MB each. Does this platform have > > > 2GB > > > > > of > > > > > > memory for real? > > > > > > > > > > > > -- > > > > > > Tom > > > > > > > > > > Yes, it does. See https://www.hardkernel.com/shop/odroid-u3/ . > > > > > > > > Thanks. I guess my current thought is that in the absence of > > > adding > > > > earlycon to the kernel args, to perhaps get more info out of the > > > kernel > > > > as to when / where it's dying, that bootm_size should be set to > > > > 0x10000000 (256MB) to replicate the old behavior, on this > > > platform. > > > > Jaehoon, do you have any other ideas? > > > > > > > > -- > > > > Tom > > >=20 > > > I was not aware of the existence of `earlycon`. Running the first > > > failing > > > commit 4963f63f with `earlycon` and with `initrd_high` *unset* > > > reveals a > > > kernel panic: > > >=20 > > > Kernel image @ 0x41000000 [ 0x000000 - 0x4be200 ] > > > ## Flattened Device Tree blob at 40800000 > > > Booting using the fdt blob at 0x40800000 > > > Loading Ramdisk to b9947000, end bae7aa21 ... OK > > > Loading Device Tree to b9936000, end b99460bf ... OK > > >=20 > > > Starting kernel ... > > >=20 > > > [ 0.000000] Booting Linux on physical CPU 0xa00 > > > [ 0.000000] Linux version 5.10.0-20-armmp > > > (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 > > > 20210110, > > > GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.158-2 > > > (2022-12-13) > > > [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 > > > (ARMv7), > > > cr=3D10c5387d > > > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT > > > aliasing > > > instruction cache > > > [ 0.000000] OF: fdt: Machine model: Hardkernel ODROID-U3 > > > board based > > > on Exynos4412 > > > [ 0.000000] earlycon: exynos4210 at MMIO 0x13810000 (options > > > '') > > > [ 0.000000] printk: bootconsole [exynos4210] enabled > > > [ 0.000000] Memory policy: Data cache writealloc > > > [ 0.000000] efi: UEFI not found. > > > [ 0.000000] Reserved memory: created DMA memory pool at > > > 0xbf700000, > > > size 8 MiB > > > [ 0.000000] OF: reserved mem: initialized node > > > region_mfc_right, > > > compatible id shared-dma-pool > > > [ 0.000000] Reserved memory: created DMA memory pool at > > > 0xbd300000, > > > size 36 MiB > > > [ 0.000000] OF: reserved mem: initialized node > > > region_mfc_left, > > > compatible id shared-dma-pool > > > [ 0.000000] cma: Reserved 16 MiB at 0xbc000000 > > > [ 0.000000] Samsung CPU ID: 0xe4412220 > > > [ 0.000000] Zone ranges: > > > [ 0.000000] DMA [mem > > > 0x0000000040000000-0x000000006fffffff] > > > [ 0.000000] Normal empty > > > [ 0.000000] HighMem [mem > > > 0x0000000070000000-0x00000000bd2fffff] > >=20 > > So here we go. Initrd cannot be in highmem. I cannot find this > > documented, quickly, under https://www.kernel.org/doc/html/latest/ so I > > guess this is more just background knowledge than formal knowledge. This > > also matches up with your noting that initrd_high=3D0x70000000 works. > >=20 > > -- > > Tom >=20 > I found this [1]. Section 5 mentions placing the initrd in lowmem, if I > understand everything correctly. Ah, right, there it is, I just skimmed too quickly. > Setting `bootm_size` to ` 0x10000000` works for me. I can write a patch t= hat > adds `bootm_size=3D0x100000000` to `CFG_EXTRA_ENV_SETTINGS` in > `include/configs/odroid.h` if you want, but I don't understand the fix, h= igh > mem and low mem well enough to write a decent commit message. I can > certainly test (a backport of, see bug reports [2], [3]) a patch. >=20 > Thanks for identifying the problem and proposing a fix! So, bootm_size is the variable which tells U-Boot that when relocating initrd/fdt around, it must be within memory start + bootm_size, as a way of enforcing the low-memory requirement (or similar constraints, aarch64 says first 1GB of memory). So technically, could set that to 0x30000000 instead of 0x10000000 which is just what the implicit limit was before the change in question. A patch as you suggest would be right, so yes, please do and thanks again for testing / digging on the platform itself! --=20 Tom --WPoY8ImOH9Y1oC7/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEGjx/cOCPqxcHgJu/FHw5/5Y0tywFAmO/T+cACgkQFHw5/5Y0 tyzrtgwAh77xKMYug8FdMvtiZimBSxM4sDsILMv9O6eDXT/L4f0flXeCOLNJBZh9 aiCV4iTorepMqlTIej+v1AA4OO/Ju/Fs/kJGYjeXcx2uHSu9QqwmnPV8Vp4i91eF MzF/WP537Bzn4kQZIEUUJ8eDl/GsOXwAVUw3oynOhTdC5r7st+hLL/7LPLL51db3 yWl6wSg4jOtAVFNsLC26nTuSu9xuvonEQzRnKW+r+eqEvTjr9PmJbbca3gCsbBJl mzqJ5rPuG7rZwi5u161d2wJt4Cj3APHdAK84jLZihJZcg9g3dB/D3Qqb5D5LyX2Y 0r0aNzzYUb+9YBh3DBSF/XjYO/K6bIGUVnATX5NRuAMsC6NKNMLecigi1afmeqtI ix8hYCsDqebSD4W1F1to5az4jxWKXlNfLCCybD+FP0352nfHFoOEwyPEqd2kZ5bu run1/zrWb6M+TZNneLrzPOO9ey0U/tLluaEdkSA0Ix7RK9TeNS539nrMA4pXfKVz V/juqqBd =KlYu -----END PGP SIGNATURE----- --WPoY8ImOH9Y1oC7/--