Naresh Kamboju <naresh.kamb...@linaro.org> writes: > The QEMU-ARMv7 boot has failed with the Linux next-20241017 tag. > The boot log is incomplete, and no kernel crash was detected. > However, the system did not proceed far enough to reach the login prompt. > > Please find the incomplete boot log links below for your reference. > The Qemu version is 9.0.2. > The arm devices TI beaglebone x15 boot pass. > > This is always reproducible. > First seen on Linux next-20241017 tag. > Good: next-20241016 > Bad: next-20241017 > > qemu-armv7: > boot: > * clang-19-lkftconfig > * gcc-13-lkftconfig > * clang-nightly-lkftconfig > > Reported-by: Linux Kernel Functional Testing <l...@linaro.org> > > Boot log: > ------- > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 0.000000] Linux version 6.12.0-rc3-next-20241017 > (tuxmake@tuxmake) (arm-linux-gnueabihf-gcc (Debian 13.3.0-5) 13.3.0, > GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP @1729156545 > [ 0.000000] CPU: ARMv7 Processor [414fc0f0] revision 0 (ARMv7), cr=10c5387d > [ 0.000000] CPU: div instructions available: patching division code > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache > [ 0.000000] OF: fdt: Machine model: linux,dummy-virt > [ 0.000000] random: crng init done > [ 0.000000] earlycon: pl11 at MMIO 0x09000000 (options '') > [ 0.000000] printk: legacy bootconsole [pl11] enabled > [ 0.000000] Memory policy: Data cache writealloc > [ 0.000000] efi: UEFI not found. > [ 0.000000] cma: Size (0x04000000) of region at 0x00000000 exceeds > limit (0x00000000) > [ 0.000000] cma: Failed to reserve 64 MiB on node -1
Is this a highmem related thing. Passing -m 2G allows it to get further and 4G is obviously at the limit of 32 bit? -- Alex Bennée Virtualisation Tech Lead @ Linaro
