From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
kvmarm@lists.linux.dev,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Fuad Tabba <tabba@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>,
Aishwarya TCV <Aishwarya.TCV@arm.com>
Subject: Re: kvm-unit-tests hang on Arm FVP with protected mode
Date: Fri, 5 Sep 2025 14:38:41 +0100 [thread overview]
Message-ID: <345e42db-eabd-4e34-abf5-d9974dfe55d1@sirena.org.uk> (raw)
In-Reply-To: <87ms79ystc.wl-maz@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On Fri, Sep 05, 2025 at 01:42:07PM +0100, Marc Zyngier wrote:
> Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > INFO: running kvm unit tests ...
> > + [ True = false ]
> > + ./run_tests.sh -a -t -v
> > + tee -a /lava-1/0/tests/0_kvm-unit-tests/automated/linux/kvm-unit-tests/output/result_log.txt
> > TAP version 13
> What do you expect us to do with such a non-report? Can you please, at
> the very least, identify which test in that test suite triggers the
> failure?
Looking at the log file that isn't password protected that's the last
line of output so it'll have hung trying to do the first test, based on
the log from another machine:
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250905/testrun/29777055/suite/kvm-unit-tests/test/debug-bp-migration-timeout-duration90s/log
it seems that should be
ok 1 - selftest-setup: selftest: setup: smp: number of CPUs matches expectation
that's died for the version they're using.
> > Links:
> > https://regressions.linaro.org/lkft/linux-mainline-master/v6.17-rc4/lava/kvm-unit-tests/history/?page=1
> What is there? This link requires a login, and goes to 11 on the
> scale of being useless.
My Linaro account appears to have been disabled at some point so I
can't access it either. If this is affecting mainline presumably it's
been an issue in at least -next for a while.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-09-05 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 12:28 kvm-unit-tests hang on Arm FVP with protected mode Naresh Kamboju
2025-09-05 12:42 ` Marc Zyngier
2025-09-05 13:38 ` Mark Brown [this message]
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=345e42db-eabd-4e34-abf5-d9974dfe55d1@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=maz@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--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