From: Will Deacon <will@kernel.org>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: catalin marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
CKI Project <cki-project@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel?5.11.0-rc7 (arm-next)
Date: Wed, 10 Feb 2021 16:09:37 +0000 [thread overview]
Message-ID: <20210210160936.GA28813@willie-the-truck> (raw)
In-Reply-To: <27613639.27281944.1612970671896.JavaMail.zimbra@redhat.com>
Hi Veronika,
Thanks for the help with this.
On Wed, Feb 10, 2021 at 10:24:31AM -0500, Veronika Kabatova wrote:
> > > On Tue, Feb 09, 2021 at 09:07:50PM -0000, CKI Project wrote:
> > > > Host 2:
> > > > ❌ Boot test
> > > > ⚡⚡⚡ selinux-policy: serge-testsuite
> > > > ⚡⚡⚡ storage: software RAID testing
> > > > 🚧 ⚡⚡⚡ xfstests - ext4
> > > > 🚧 ⚡⚡⚡ xfstests - xfs
> > > > 🚧 ⚡⚡⚡ xfstests - btrfs
> > > > 🚧 ⚡⚡⚡ IPMI driver test
> > > > 🚧 ⚡⚡⚡ IPMItool loop stress test
> > > > 🚧 ⚡⚡⚡ Storage blktests
> > > > 🚧 ⚡⚡⚡ Storage block - filesystem fio test
> > > > 🚧 ⚡⚡⚡ Storage block - queue scheduler test
> > > > 🚧 ⚡⚡⚡ Storage nvme - tcp
> > > > 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
> > > > 🚧 ⚡⚡⚡ stress: stress-ng
> > >
> > > Which system (e.g. soc) is host 2 and are there are known infra issues at
> > > the moment? I did push some changes which affect the early boot path, so we
> > > may well be running into a kernel bug, but I'd just like to make sure
> > > before
> > > we dive in trying to debug that, especially as we haven't seen failures on
> > > other systems (and host 1 seems ok).
> > >
> >
> > Hi, the machine in question is a Cavium ThunderX2 Sabre. It booted a stable
> > kernel just a few days back okay. The last messages I can see in the raw
> > console log from this run are:
> >
> > EFI stub: Booting Linux Kernel...
> > EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled
> > EFI stub: Using DTB from configuration table
> > EFI stub: Exiting boot services and installing virtual address map...
> >
> > and then it times out after hour and half. I'm not aware of any ongoing
> > issues, however sometimes the link between the lab controller and the
> > machines can sometimes go wrong after reboot and lead to a similarly
> > looking problem.
> >
> > I'll resubmit the test job on that same machine to check if that was
> > the case and let you know right after it boots.
> >
>
> Hi, I have a few results back:
>
> - resubmitted the same kernel: gets stuck in the same spot
> - tried the new version pushed today: gets stuck in the same spot
That's odd, as I just received a pass report for that branch!
https://lore.kernel.org/r/cki.598435E2D5.M3C5MKJ1NV@redhat.com
Is it just flakey, perhaps? Obviously, that's not great either, but it will
make bisection more challenging.
> - tried the version from last week: boots ok
>
> There is an extra message from the run that managed to boot, which is not
> present with any of the runs that failed:
>
> EFI stub: ERROR: FIRMWARE BUG: efi_loaded_image_t::image_base has bogus value
>
> But this message is not present with the stable run that I mentioned
> previously.
Interesting. Are those messages in the logs anywhere? It would be handy to
include them, if possible.
Cheers,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-10 16:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 21:07 ❌ FAIL: Test report for kernel 5.11.0-rc7 (arm-next) CKI Project
2021-02-10 9:29 ` Will Deacon
2021-02-10 12:01 ` Veronika Kabatova
2021-02-10 15:24 ` Veronika Kabatova
2021-02-10 16:09 ` Will Deacon [this message]
2021-02-10 17:07 ` ❌ FAIL: Test report for kernel?5.11.0-rc7 (arm-next) Veronika Kabatova
2021-02-10 17:31 ` ❌ FAIL: Test report for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 18:06 ` Veronika Kabatova
2021-02-10 18:56 ` ❌ FAIL: Test report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 19:31 ` Veronika Kabatova
2021-02-10 20:17 ` ❌ FAIL: Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 20:32 ` Will Deacon
2021-02-11 10:46 ` Veronika Kabatova
2021-02-11 11:50 ` ❌ FAIL:?Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-11 12:25 ` Veronika Kabatova
2021-02-15 13:13 ` Veronika Kabatova
2021-02-15 18:24 ` Will Deacon
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=20210210160936.GA28813@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vkabatov@redhat.com \
/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).