From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
heiko@sntech.de, srinivas.kandagatla@linaro.org,
nicolas.frattaroli@collabora.com
Subject: Re: [linux-next-20250307] Build Failure
Date: Tue, 11 Mar 2025 09:53:23 +0530 [thread overview]
Message-ID: <25306d01-db9d-42aa-9c26-2e18dfc30241@linux.ibm.com> (raw)
In-Reply-To: <70ba4e80-53c4-4583-82f3-2851e0829aa6@linux.ibm.com>
Git Bisect is poinitng to commit:
3e081aa132bbefe31ac95dd6dfc8d787ffa83d0b as first bad commit.
Git bisect log:
git bisect start
# status: waiting for both good and bad commits
# bad: [0a2f889128969dab41861b6e40111aa03dc57014] Add linux-next
specific files for 20250307
git bisect bad 0a2f889128969dab41861b6e40111aa03dc57014
# status: waiting for good commit(s), bad commit known
# good: [7eb172143d5508b4da468ed59ee857c6e5e01da6] Linux 6.14-rc5
git bisect good 7eb172143d5508b4da468ed59ee857c6e5e01da6
# good: [7eb172143d5508b4da468ed59ee857c6e5e01da6] Linux 6.14-rc5
git bisect good 7eb172143d5508b4da468ed59ee857c6e5e01da6
# good: [80ec13b98c6378cbf9b29d7ee7d3db930ddbd858] Merge branch 'master'
of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
git bisect good 80ec13b98c6378cbf9b29d7ee7d3db930ddbd858
# good: [6c60220c45270869a7c5f791f6e0197b1f0d0388] Merge branch
'driver-core-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
git bisect good 6c60220c45270869a7c5f791f6e0197b1f0d0388
# good: [187734f508b0a9a00ccaaf7d8ba05874b624ac73] Merge branch
'for-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
git bisect good 187734f508b0a9a00ccaaf7d8ba05874b624ac73
# good: [316ff3a28679b82eb2bf17c02dbca970e7433182] Merge branch
'for-next/seccomp' of
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git bisect good 316ff3a28679b82eb2bf17c02dbca970e7433182
# bad: [69759c9d8dd7df716dcca3601b82e5618332cef7] Merge branch
'rust-next' of https://github.com/Rust-for-Linux/linux.git
git bisect bad 69759c9d8dd7df716dcca3601b82e5618332cef7
# bad: [1e4eee5176c91b00e73cee90712a995668020a9c] Merge branch
'mhi-next' of git://git.kernel.org/pub/scm/linux/kernel/git/mani/mhi.git
git bisect bad 1e4eee5176c91b00e73cee90712a995668020a9c
# bad: [962bc2aae4f4295314d4a5f5c59a465f97f8b59a] Merge branch
'for-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-auxdisplay.git
git bisect bad 962bc2aae4f4295314d4a5f5c59a465f97f8b59a
# bad: [612fd001319aae2b514fc234939806cf3294dbba] Merge branch 'main' of
git://git.infradead.org/users/willy/xarray.git
git bisect bad 612fd001319aae2b514fc234939806cf3294dbba
# bad: [f5175dd69428ab517c8d68e772c4d287b6570d8e] dt-bindings: nvmem:
fixed-cell: increase bits start value to 31
git bisect bad f5175dd69428ab517c8d68e772c4d287b6570d8e
# bad: [8c94337ebbfb840944574f82df0cbe35930d8df8] dt-bindings: nvmem:
rockchip,otp: Add compatible for RK3576
git bisect bad 8c94337ebbfb840944574f82df0cbe35930d8df8
# bad: [024e21343f3cbcde0343473fcaf094d2c19cc7bf] nvmem: rockchip-otp:
Move read-offset into variant-data
git bisect bad 024e21343f3cbcde0343473fcaf094d2c19cc7bf
# bad: [3e081aa132bbefe31ac95dd6dfc8d787ffa83d0b] clk: rockchip: rk3576:
define clk_otp_phy_g
git bisect bad 3e081aa132bbefe31ac95dd6dfc8d787ffa83d0b
# first bad commit: [3e081aa132bbefe31ac95dd6dfc8d787ffa83d0b] clk:
rockchip: rk3576: define clk_otp_phy_g
On 09/03/25 6:08 pm, Venkat Rao Bagalkote wrote:
> Greetings!!,
>
> I see linux-next-20250307 fails to build on IBM Power9 and Power10
> servers.
>
>
> Errors:
>
> In file included from ^[[01m^[[K<command-line>^[[m^[[K:
> ^[[01m^[[K./usr/include/cxl/features.h:11:10:^[[m^[[K
> ^[[01;31m^[[Kfatal error: ^[[m^[[Kuuid/uuid.h: No such file or directory
> 11 | #include ^[[01;31m^[[K<uuid/uuid.h>^[[m^[[K
> | ^[[01;31m^[[K^~~~~~~~~~~~~^[[m^[[K
> compilation terminated.
> make[4]: *** [usr/include/Makefile:85:
> usr/include/cxl/features.hdrtest] Error 1
> make[3]: *** [scripts/Makefile.build:461: usr/include] Error 2
> make[2]: *** [scripts/Makefile.build:461: usr] Error 2
> make[2]: *** Waiting for unfinished jobs....
> arch/powerpc/kernel/switch.o: warning: objtool: .text+0x4:
> intra_function_call not a direct call
> arch/powerpc/crypto/ghashp8-ppc.o: warning: objtool: .text+0x22c:
> unannotated intra-function call
> arch/powerpc/kvm/book3s_hv_rmhandlers.o: warning: objtool:
> .text+0xe84: intra_function_call not a direct call
> make[1]: *** [/home/linux_src/linux/Makefile:1997: .] Error 2
> make: *** [Makefile:251: __sub-make] Error 2
>
> Please add below tag, if you happen to fix this issue.
>
> Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
>
>
> Regards,
>
> Venkat.
>
next prev parent reply other threads:[~2025-03-11 4:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 12:38 [linux-next-20250307] Build Failure Venkat Rao Bagalkote
2025-03-11 4:23 ` Venkat Rao Bagalkote [this message]
2025-03-11 7:41 ` Nicolas Frattaroli
2025-03-11 8:47 ` Madhavan Srinivasan
2025-03-11 9:40 ` Madhavan Srinivasan
2025-03-11 22:50 ` Christophe Leroy
2025-03-12 10:11 ` Venkat Rao Bagalkote
2025-03-12 10:16 ` Christophe Leroy
2025-03-17 7:19 ` Venkat Rao Bagalkote
2025-03-12 15:19 ` Christophe Leroy
2025-03-17 7:27 ` Venkat Rao Bagalkote
2025-03-17 10:06 ` Christophe Leroy
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=25306d01-db9d-42aa-9c26-2e18dfc30241@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=nicolas.frattaroli@collabora.com \
--cc=sfr@canb.auug.org.au \
--cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).