From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Aishwarya TCV <Aishwarya.TCV@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: arm64: defconfig build failed on Linux next-20220721
Date: Thu, 21 Jul 2022 15:02:33 +0100 [thread overview]
Message-ID: <87zgh2y35y.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+G9fYsuUdyUUUa_Xcfzfnh+Y8c82LnjeHum31C2ancBdxswCQ@mail.gmail.com>
On Thu, 21 Jul 2022 14:53:03 +0100,
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> arm64 defconfig build failed on Linux next-20220721 tag kernel.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Regressions found on arm64:
> - build-gcc-11-lkftconfig-64k_page_size
> - build-gcc-11-lkftconfig-rcutorture
> - build-gcc-11-lkftconfig-devicetree
> - build-gcc-11-lkftconfig
> - build-gcc-11-lkftconfig-debug
> - build-gcc-11-lkftconfig-armv8_features
> - build-gcc-11-lkftconfig-kselftest
> - build-gcc-11-lkftconfig-kunit
> - build-gcc-11-lkftconfig-libgpiod
> - build-gcc-11-lkftconfig-kasan
> - build-clang-12-lkftconfig
> - build-clang-14-lkftconfig
> - build-clang-13-lkftconfig
> - build-clang-nightly-lkftconfig
> - build-gcc-11-lkftconfig-debug-kmemleak
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build
> CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
> /builds/linux/arch/arm64/kernel/head.S: Assembler messages:
> /builds/linux/arch/arm64/kernel/head.S:334: Error: immediate cannot be
> moved by a single instruction
See https://lore.kernel.org/r/20220721124244.903567-1-maz@kernel.org
as a potential workaround.
Another solution would be to have Peter's patch in 5.19 but not in
5.20.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Aishwarya TCV <Aishwarya.TCV@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: arm64: defconfig build failed on Linux next-20220721
Date: Thu, 21 Jul 2022 15:02:33 +0100 [thread overview]
Message-ID: <87zgh2y35y.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+G9fYsuUdyUUUa_Xcfzfnh+Y8c82LnjeHum31C2ancBdxswCQ@mail.gmail.com>
On Thu, 21 Jul 2022 14:53:03 +0100,
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> arm64 defconfig build failed on Linux next-20220721 tag kernel.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Regressions found on arm64:
> - build-gcc-11-lkftconfig-64k_page_size
> - build-gcc-11-lkftconfig-rcutorture
> - build-gcc-11-lkftconfig-devicetree
> - build-gcc-11-lkftconfig
> - build-gcc-11-lkftconfig-debug
> - build-gcc-11-lkftconfig-armv8_features
> - build-gcc-11-lkftconfig-kselftest
> - build-gcc-11-lkftconfig-kunit
> - build-gcc-11-lkftconfig-libgpiod
> - build-gcc-11-lkftconfig-kasan
> - build-clang-12-lkftconfig
> - build-clang-14-lkftconfig
> - build-clang-13-lkftconfig
> - build-clang-nightly-lkftconfig
> - build-gcc-11-lkftconfig-debug-kmemleak
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build
> CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
> /builds/linux/arch/arm64/kernel/head.S: Assembler messages:
> /builds/linux/arch/arm64/kernel/head.S:334: Error: immediate cannot be
> moved by a single instruction
See https://lore.kernel.org/r/20220721124244.903567-1-maz@kernel.org
as a potential workaround.
Another solution would be to have Peter's patch in 5.19 but not in
5.20.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
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:[~2022-07-21 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:53 arm64: defconfig build failed on Linux next-20220721 Naresh Kamboju
2022-07-21 13:53 ` Naresh Kamboju
2022-07-21 14:02 ` Marc Zyngier [this message]
2022-07-21 14:02 ` Marc Zyngier
2022-07-22 7:18 ` Naresh Kamboju
2022-07-22 7:18 ` Naresh Kamboju
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=87zgh2y35y.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.