On Fri, Oct 18, 2024 at 12:56:01PM +0530, Naresh Kamboju wrote: > 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 <l...@linaro.org> > > Boot log: > --------- > [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510] > [ 0.000000] Linux version 6.12.0-rc3-next-20241017 > (tuxmake@tuxmake) (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>
Qemu bug. See this email from Peter: https://lore.kernel.org/r/cafeaca8ujl1t2mdjajl7u5ow4ns23_e+sk7987x4gacs3ds...@mail.gmail.com -- Catalin
