From: Catalin Marinas <catalin.marinas@arm.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list" <linux-kernel@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
qemu-devel@nongnu.org, lkft-triage@lists.linaro.org,
"Linux Regressions" <regressions@lists.linux.dev>,
"Mark Brown" <broonie@kernel.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Aishwarya TCV" <aishwarya.tcv@arm.com>
Subject: Re: Qemu v9.0.2: Boot failed qemu-arm64 with Linux next-20241017 tag
Date: Fri, 18 Oct 2024 10:21:57 +0100 [thread overview]
Message-ID: <ZxIotWFxJf8H9bYX@arm.com> (raw)
In-Reply-To: <CA+G9fYvx05D7TfRjvdPtKM9iWS6i7b-EHuBAbHEQghvMEg221g@mail.gmail.com>
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 <lkft@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+sk7987x4gAcs3dSZOw@mail.gmail.com
--
Catalin
next prev parent reply other threads:[~2024-10-18 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 7:26 Qemu v9.0.2: Boot failed qemu-arm64 with Linux next-20241017 tag Naresh Kamboju
2024-10-18 9:21 ` Catalin Marinas [this message]
2024-10-18 9:46 ` Alex Bennée
2024-10-18 9:48 ` Peter Maydell
2024-10-18 10:22 ` Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxIotWFxJf8H9bYX@arm.com \
--to=catalin.marinas@arm.com \
--cc=aishwarya.tcv@arm.com \
--cc=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.