public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Eric Biederman <ebiederm@xmission.com>,
	kexec@lists.infradead.org,
	open list <linux-kernel@vger.kernel.org>,
	linux-stable <stable@vger.kernel.org>,
	Sasha Levin <sashal@kernel.org>,
	lkft-triage@lists.linaro.org
Subject: Re: kernel/kexec_file.o: failed: Cannot find symbol for section 10: .text.unlikely.
Date: Sun, 5 Sep 2021 16:58:23 +0200	[thread overview]
Message-ID: <YTTbD+BKRpd0g4hq@kroah.com> (raw)
In-Reply-To: <CA+G9fYvMaHgSied79QBs3D=eDVETGH=3gxA8owCSRj313yEhVg@mail.gmail.com>

On Sun, Sep 05, 2021 at 07:28:35PM +0530, Naresh Kamboju wrote:
> Following build errors noticed while building stable rc Linux 5.13.14
> with gcc-11 for powerpc architecture.
> 
> # to reproduce this build locally:
> tuxmake --target-arch=powerpc --kconfig=defconfig --toolchain=gcc-11
> --wrapper=sccache --environment=KBUILD_BUILD_TIMESTAMP=@1630691419
> --environment=KBUILD_BUILD_USER=tuxmake
> --environment=KBUILD_BUILD_HOST=tuxmake
> --environment=SCCACHE_BUCKET=sccache.tuxbuild.com --runtime=podman
> --image=855116176053.dkr.ecr.us-east-1.amazonaws.com/tuxmake/powerpc_gcc-11
> config default kernel xipkernel modules dtbs dtbs-legacy debugkernel
> headers
> 
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/current ARCH=powerpc
> CROSS_COMPILE=powerpc64le-linux-gnu- 'CC=sccache
> powerpc64le-linux-gnu-gcc' 'HOSTCC=sccache gcc' defconfig
> 
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/current ARCH=powerpc
> CROSS_COMPILE=powerpc64le-linux-gnu- 'CC=sccache
> powerpc64le-linux-gnu-gcc' 'HOSTCC=sccache gcc'
> Cannot find symbol for section 10: .text.unlikely.
> kernel/kexec_file.o: failed
> make[2]: *** [/builds/linux/scripts/Makefile.build:273:
> kernel/kexec_file.o] Error 1
> make[2]: *** Deleting file 'kernel/kexec_file.o'
> 
> 
> Build config:
> https://builds.tuxbuild.com/1xdiIZVZuLCW3X1WO2YT6Fsl19w/config
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> meta data:
> -----------
>     git_repo: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
>     git_sha: a603798fb16829e56f80f57879611e67bba4910d
>     git_short_log: a603798fb168 (\Linux 5.13.14\)
>     kconfig:  defconfig
>     kernel_version: 5.13.14
>     target_arch: powerpc
>     toolchain: gcc-11
> 
> steps to reproduce:
> https://builds.tuxbuild.com/1xdiIZVZuLCW3X1WO2YT6Fsl19w/tuxmake_reproducer.sh
> 
> --
> Linaro LKFT
> https://lkft.linaro.org

Is this a regression?  Has this compiler ever been able to build this
arch like this?

thanks,

greg k-h

  reply	other threads:[~2021-09-05 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 13:58 kernel/kexec_file.o: failed: Cannot find symbol for section 10: .text.unlikely Naresh Kamboju
2021-09-05 14:58 ` Greg Kroah-Hartman [this message]
2021-09-06  7:40   ` Naresh Kamboju
2021-09-06  8:09     ` Greg Kroah-Hartman
2021-09-06  8:49       ` Naresh Kamboju
2021-09-07  6:14         ` 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=YTTbD+BKRpd0g4hq@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sashal@kernel.org \
    --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