From: Veronika Kabatova <vkabatov@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Cc: CKI Project <cki-project@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel 5.8.10 (stable-queue)
Date: Thu, 17 Sep 2020 12:58:51 -0400 (EDT) [thread overview]
Message-ID: <844826791.11580305.1600361931814.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <cki.6E3AFCFF18.F6R74WI3JM@redhat.com>
----- Original Message -----
> From: "CKI Project" <cki-project@redhat.com>
> To: "Linux Stable maillist" <stable@vger.kernel.org>
> Sent: Thursday, September 17, 2020 6:53:13 PM
> Subject: ❌ FAIL: Test report for kernel 5.8.10 (stable-queue)
>
>
> Hello,
>
> We ran automated tests on a recent commit from this kernel tree:
>
> Kernel repo:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> Commit: 64d351e12747 - loop: Set correct device size when using
> LOOP_CONFIGURE
>
> The results of these automated tests are provided below.
>
> Overall result: FAILED (see details below)
> Merge: OK
> Compile: 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/2020/09/17/613941
>
> We attempted to compile the kernel for multiple architectures, but the
> compile
> failed on one or more architectures:
>
> ppc64le: FAILED (see build-ppc64le.log.xz attachment)
>
Hi, the artifact uploads are suffering some issues right now so I'm including
the log excerpt here:
...
00:04:31 MODINFO modules.builtin.modinfo
00:04:32 GEN modules.builtin
00:04:32 LD .tmp_vmlinux.kallsyms1
00:04:33 powerpc64le-linux-gnu-ld: arch/powerpc/kernel/cputable.o:(.init.data+0xd78): undefined reference to `__machine_check_early_realmode_p10'
00:04:33 make[2]: *** [Makefile:1135: vmlinux] Error 1
00:04:33 make[1]: *** [scripts/Makefile.package:109: targz-pkg] Error 2
00:04:33 make: *** [Makefile:1491: targz-pkg] Error 2
This seems to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=72f26692391f65ea65fc46b6cdae128734283946
The kernel misses the function, it mainline it was included in:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=201220bb0e8cb
Veronika
> We hope that these logs can help you find the problem quickly. For the full
> detail on our testing procedures, please scroll to the bottom of this
> message.
>
> Please reply to this email if you have any questions about the tests that we
> ran or if you have any suggestions on how to make future tests more
> effective.
>
> ,-. ,-.
> ( C ) ( K ) Continuous
> `-',-.`-' Kernel
> ( I ) Integration
> `-'
> ______________________________________________________________________________
>
> Compile testing
> ---------------
>
> We compiled the kernel for 4 architectures:
>
> aarch64:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> ppc64le:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> s390x:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> x86_64:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
>
>
prev parent reply other threads:[~2020-09-17 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 16:53 ❌ FAIL: Test report for kernel 5.8.10 (stable-queue) CKI Project
2020-09-17 16:58 ` Veronika Kabatova [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=844826791.11580305.1600361931814.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=cki-project@redhat.com \
--cc=stable@vger.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