linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: CKI Project <cki-project@redhat.com>,
	ardb@kernel.org, lorenzo.pieralisi@arm.com,
	anshuman.khandual@arm.com, mark.rutland@arm.com, maz@kernel.org
Cc: skt-results-master@redhat.com, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org,
	Memory Management <mm-qe@redhat.com>,
	Jan Stancek <jstancek@redhat.com>,
	Fendy Tjahjadi <ftjahjad@redhat.com>,
	Jeff Bastian <jbastian@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel 5.13.0-rc4 (arm-next, 8124c8a6)
Date: Wed, 2 Jun 2021 11:12:27 +0100	[thread overview]
Message-ID: <20210602101227.GB30503@willie-the-truck> (raw)
In-Reply-To: <cki.9F9FE56EEB.62MGF3Q8H6@redhat.com>

Hi all,

On Wed, Jun 02, 2021 at 01:35:01AM -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: 8124c8a6b353 - Linux 5.13-rc4

As above, this is a run against plain -rc4 in preparation for testing the
5.14 queue on top to detect any regressions.

> 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/06/01/313156257
> 
> One or more kernel tests failed:
> 
>     aarch64:
>      ❌ LTP

The two tests failing here are 'statx04' and 'hugeshmat04':

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/06/01/313156257/build_aarch64_redhat%3A1310052388/tests/LTP/10079826_aarch64_1_resultoutputfile.log

(grep for FAIL). I've not had a chance to dig into them yet.

>      💥 stress: stress-ng

This explodes pretty badly. Some CPUs detect RCU stalls when trying to use
the EFI "efi_read_time" service, which eventually fails but soon after we
explode trying to access memory which I think is mapped by
acpi_os_ioremap(), so it looks like the f/w might be the culprit here. Is
the "HPE Apollo 70" machine known to have bad EFI firmware?

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/06/01/313156257/build_aarch64_redhat%3A1310052388/tests/stress_stress_ng/10079827_aarch64_2_dmesg.log

(scroll to the end for the fireworks)

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-02 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  1:35 ❌ FAIL: Test report for kernel 5.13.0-rc4 (arm-next, 8124c8a6) CKI Project
2021-06-02 10:12 ` Will Deacon [this message]
2021-06-02 10:34   ` ? " Mark Rutland
     [not found]   ` <CAMj1kXENsUScpTg294HDiQUUXuUBz438hysEM9M4N-Jcq+q2fA@mail.gmail.com>
2021-06-02 10:51     `  " Will Deacon
     [not found]       ` <CA+tGwnn+9XCDB69LxY1AEoNih_qCovwYsuNHzbwyUN8LmZTTAg@mail.gmail.com>
2021-06-02 17:10         ` Will Deacon
     [not found]           ` <CA+tGwn=Y63hMdHpP16i4YD1qx-hwnSxfWsNgC+Kh-SDxXZpqGA@mail.gmail.com>
     [not found]             ` <CA+tGwn=BG6nUQcs_Q2a1h=UDPwR6ern2wQPwQ84kz=c2xB5-Wg@mail.gmail.com>
2021-06-11 10:34               ` 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=20210602101227.GB30503@willie-the-truck \
    --to=will@kernel.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=ftjahjad@redhat.com \
    --cc=jbastian@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=mm-qe@redhat.com \
    --cc=skt-results-master@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).