[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYvx05D7TfRjvdPtKM9iWS6i7b-EHuBAbHEQghvMEg221g@mail.gmail.com>
Date: Fri, 18 Oct 2024 12:56:01 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: open list <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>, qemu-devel@...gnu.org,
lkft-triage@...ts.linaro.org, Linux Regressions <regressions@...ts.linux.dev>
Cc: Catalin Marinas <catalin.marinas@....com>, Mark Brown <broonie@...nel.org>,
Alex Bennée <alex.bennee@...aro.org>,
Peter Maydell <peter.maydell@...aro.org>, Anders Roxell <anders.roxell@...aro.org>,
Arnd Bergmann <arnd@...db.de>, Dan Carpenter <dan.carpenter@...aro.org>,
Aishwarya TCV <aishwarya.tcv@....com>
Subject: Qemu v9.0.2: Boot failed qemu-arm64 with Linux next-20241017 tag
The QEMU-arm64 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 arm64 devices boot pass.
This is always reproducible.
First seen on Linux next-20241017 tag.
Good: next-20241016
Bad: next-20241017
qemu-arm64-protected:
boot:
* clang-19-lkftconfig
* gcc-13-lkftconfig
* clang-nightly-lkftconfig
Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
Boot log:
---------
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510]
[ 0.000000] Linux version 6.12.0-rc3-next-20241017
(tuxmake@...make) (Debian clang version 19.1.2
(++20241001023520+d5498c39fe6a-1~exp1~20241001143639.51), Debian LLD
19.1.2) #1 SMP PREEMPT @1729156545
[ 0.000000] KASLR enabled
[ 0.000000] random: crng init done
[ 0.000000] Machine model: linux,dummy-virt
[ 0.000000] efi: UEFI not found.
[ 0.000000] Capping linear region to 51 bits for KVM in nVHE mode
on LVA capable hardware.
...
[ 0.000000] Kernel command line: console=ttyAMA0,115200 rootwait
root=/dev/vda debug verbose console_msg_format=syslog
systemd.log_level=warning rw kvm-arm.mode=protected earlycon
...
<6>[ 0.305549] SME: maximum available vector length 256 bytes per vector
<6>[ 0.306214] SME: default vector length 32 bytes per vector
**
ERROR:target/arm/internals.h:923:regime_is_user: code should not be reached
Bail out! ERROR:target/arm/internals.h:923:regime_is_user: code should
not be reached
<nothing after this>
Boot failed log links,
-------------
dmesg log: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241017/testrun/25475692/suite/boot/test/clang-19-lkftconfig/log
test details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241017/testrun/25475692/suite/boot/test/clang-19-lkftconfig/details/
Build image:
-----------
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2nYi294C2rkwmj8hWZ0XnFcTd7F/
Steps to reproduce:
------------
/usr/bin/qemu-system-aarch64 -cpu max,pauth-impdef=on \
-machine virt,virtualization=on,gic-version=3,mte=on \
-nographic -nic none -m 4G -monitor none -no-reboot -smp 2 \
-kernel Image -append \"console=ttyAMA0,115200 rootwait
root=/dev/vda debug verbose console_msg_format=syslog
systemd.log_level=warning rw kvm-arm.mode=protected earlycon\" \
-drive file=arm64_rootfs.ext4,if=none,format=raw,id=hd0 -device
virtio-blk-device,drive=hd0
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/builds/2nYi294C2rkwmj8hWZ0XnFcTd7F/config
build url: https://storage.tuxsuite.com/public/linaro/lkft/builds/2nYi294C2rkwmj8hWZ0XnFcTd7F/
toolchain: clang-19, gcc-13 and clang-nightly
config: defconfig
arch: arm64
--
Linaro LKFT
https://lkft.linaro.org
Powered by blists - more mailing lists