On Fri, 18 Oct 2024 at 12:35, Naresh Kamboju <naresh.kamb...@linaro.org> wrote:
>
> 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
Anders bisected this boot regressions and found,
# first bad commit:
[efe8419ae78d65e83edc31aad74b605c12e7d60c]
vdso: Introduce vdso/page.h
We are investigating the reason for boot failure due to this commit.
Anyone have noticed a similar qemu-arm boot regressions with
the Linux next-20241017 and next-20241018 tags ?
> 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
>
> <nothing after this>
>
> Boot log link,
> -----
> -
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241017/testrun/25476340/suite/boot/test/clang-19-lkftconfig/log
> -
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241017/testrun/25476340/suite/boot/test/clang-19-lkftconfig/details/
>
> Build images:
> ------
> -
> https://storage.tuxsuite.com/public/linaro/lkft/tests/2nYi2nidfMq35VigDlxJblZzokr/
>
> Steps to reproduce via qemu:
> ----------------
> /usr/bin/qemu-system-arm -cpu cortex-a15 \
> -machine virt,gic-version=3 \
> -nographic -nic none -m 4G -monitor \
> none -no-reboot -smp 2 \
> -kernel zImage \
> -append \"console=ttyAMA0,115200 rootwait root=/dev/vda
> debug verbose console_msg_format=syslog systemd.log_level=warning rw
> earlycon\"
> -drive
> file=debian_trixie_armhf_rootfs.ext4,if=none,format=raw,id=hd0 \
> -device virtio-blk-device,drive=hd0
>
> Steps to reproduce with tuxrun reproducer:
> ---------------
> -
> https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2nYi2nidfMq35VigDlxJblZzokr/reproducer
>
> Boot history compare link:
> ------------------------
> -
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241017/testrun/25476340/suite/boot/test/clang-19-lkftconfig/history/
>
> metadata:
> ----
> git describe: next-20241017
> git repo:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git sha: 7df1e7189cecb6965ce672e820a5ec6cf499b65b
> kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/tests/2nYi2nidfMq35VigDlxJblZzokr/config
> build url:
> https://storage.tuxsuite.com/public/linaro/lkft/tests/2nYi2nidfMq35VigDlxJblZzokr/
> toolchain: clang-19, gcc-13 and clang-nightly
> config: lkftconfig
> arch: arm
>
> --
> Linaro LKFT
> https://lkft.linaro.org
- Naresh
