From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "kernelci.org bot" <bot@kernelci.org>,
will@kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: Re: arm64/for-kernelci baseline: 14 runs, 4 regressions (v6.12-rc3-67-gb9e20acb61ba)
Date: Thu, 17 Oct 2024 13:12:58 +0100 [thread overview]
Message-ID: <ZxD_ShjO8CyjGj5U@arm.com> (raw)
In-Reply-To: <CAFEAcA9k+EfOuk7BFcUatHsDaYKE3Ze79FTVnJZA9yaZ7QopGQ@mail.gmail.com>
On Thu, Oct 17, 2024 at 12:50:42PM +0100, Peter Maydell wrote:
> On Thu, 17 Oct 2024 at 12:34, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On Wed, Oct 16, 2024 at 11:59:02AM -0700, kernelci.org bot wrote:
> > > Test Regressions
> > > ----------------
> > >
> > >
> > > platform | arch | lab | compiler | defconfig | regressions
> > > ---------------------------+-------+-------------+----------+-----------+------------
> > > qemu_arm64-virt-gicv2 | arm64 | lab-broonie | gcc-12 | defconfig | 1
> > >
> > > Details: https://kernelci.org/test/plan/id/671002a4ff09627193c86863
> >
> > This page is still 404 (it happens quite a lot even with the logs in
> > these reports, not really helpful).
> >
> > >
> > > Results: 0 PASS, 1 FAIL, 0 SKIP
> > > Full config: defconfig
> > > Compiler: gcc-12 (aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0)
> > > Plain log: https://storage.kernelci.org//arm64/for-kernelci/v6.12-rc3-67-gb9e20acb61ba/arm64/defconfig/gcc-12/lab-broonie/baseline-qemu_arm64-virt-gicv2.txt
> > > HTML log: https://storage.kernelci.org//arm64/for-kernelci/v6.12-rc3-67-gb9e20acb61ba/arm64/defconfig/gcc-12/lab-broonie/baseline-qemu_arm64-virt-gicv2.html
> > > Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230703.0/arm64/rootfs.cpio.gz
> >
> > At least the boot log is shown (for this email, others point to missing
> > pages). However, it looks more like a Qemu bug, something about SME it
> > doesn't like:
> >
> > 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
> >
> > I tried Qemu 7.2.0 and 8.2.4, both from Debian (stable and unstable).
> > Adding Peter, maybe he has any idea.
>
> Yeah, we shouldn't be hitting asserts (to state the obvious).
>
> If you can provide the QEMU command line and the kernel/etc
> files needed to run it, I can have a look.
The kernel defconfig should be sufficient to trigger it. It must be the
for-kernelci branch from here:
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/
My qemu command line is:
qemu-system-aarch64 \
-machine virt,gic_version=3,mte=on \
-cpu max \
-smp 2 -m 2G \
-kernel </path/to/Image> \
-semihosting -nographic \
-serial mon:stdio \
-monitor tcp:0.0.0.0:4000,server,nowait \
-netdev user,id=net0,hostfwd=tcp:0.0.0.0:4022-:22 \
-device virtio-net-device,netdev=net0 \
-object rng-random,filename=/dev/urandom,id=rng0 \
-device virtio-rng-pci,rng=rng0 \
-append 'console=ttyAMA0 earlycon=pl011,0x9000000 loglevel=9 ip=dhcp root=/dev/nfs rw nfsroot=<ip-addr>:/srv/nfs/debian-arm64,tcp,v4 kasan.mode=sync'
You don't need a filesystem, it fails before reaching that point. I
guess all it matters is '-cpu max'.
Thanks.
--
Catalin
next prev parent reply other threads:[~2024-10-17 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 18:59 arm64/for-kernelci baseline: 14 runs, 4 regressions (v6.12-rc3-67-gb9e20acb61ba) kernelci.org bot
2024-10-17 11:34 ` Catalin Marinas
2024-10-17 11:50 ` Peter Maydell
2024-10-17 12:12 ` Catalin Marinas [this message]
2024-10-17 17:27 ` Peter Maydell
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=ZxD_ShjO8CyjGj5U@arm.com \
--to=catalin.marinas@arm.com \
--cc=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peter.maydell@linaro.org \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).