Re: ❌ FAIL: Test report for kernel 5.11.0-rc7 (arm-next)

[Veronika Kabatova]

----- Original Message -----
> From: "Will Deacon" <will at kernel.org>
> To: "CKI Project" <cki-project at redhat.com>
> Cc: "catalin marinas" <catalin.marinas at arm.com>, linux-arm-kernel at lists.infradead.org
> Sent: Wednesday, February 10, 2021 10:29:46 AM
> Subject: Re: ❌ FAIL: Test report for kernel	5.11.0-rc7 (arm-next)
> 
> Hi CKI folks,
> 
> Please can you help me with the error below?
> 
> On Tue, Feb 09, 2021 at 09:07:50PM -0000, CKI Project wrote:
> > We ran automated tests on a recent commit from this kernel tree:
> > 
> >        Kernel repo:
> >        https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> >             Commit: 4176e42aa565 - Merge branch 'for-next/cpufeature' into
> >             for-kernelci
> > 
> > The results of these automated tests are provided below.
> > 
> >     Overall result: FAILED (see details below)
> >              Merge: OK
> >            Compile: OK
> >              Tests: FAILED
> > 
> > All kernel binaries, config files, and logs are available for download
> > here:
> > 
> >   https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/09/623431
> > 
> > One or more kernel tests failed:
> > 
> >     aarch64:
> >      ❌ Boot test
> 
> [...]
> 
> >     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.


Veronika

> In the meantime, I'll push a new branch without those early changes to see
> if that does any better.
> 
> Thanks,
> 
> Will
> 
> 
>