From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
namhyung@kernel.org
Subject: Re: linux-next: build failure after merge of the perf tree
Date: Tue, 28 Mar 2023 16:47:23 -0300 [thread overview]
Message-ID: <ZCNES6N7AkskjD0o@kernel.org> (raw)
In-Reply-To: <20230328123332.0a3e2b6d@canb.auug.org.au>
Em Tue, Mar 28, 2023 at 12:33:32PM +1100, Stephen Rothwell escreveu:
> Hi Arnaldo,
>
> Just a few datapoints:
>
> My build machine (Debian Testing PowerpcLE, not quite the latest
> kernel):
> On Thu, 23 Mar 2023 10:27:36 -0300 Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Which improves a bit the situation.
> >
> > We could check if bpftool is available and if not, suggest installing
> > it.
>
> $ ls -l /usr/sbin/bpftool
> -rwxr-xr-x 1 root root 790504 Mar 6 02:33 /usr/sbin/bpftool
>
> > If it is available, we could check if /sys/kernel/bpf/ is available, if
> > not suggest using a kernel with CONFIG_DEBUG_INFO_BTF=y, as most distros
> > have by now.
The config files you used don't match the running kernels
> $ uname -a
> Linux zz1 6.0.0-5-powerpc64le #1 SMP Debian 6.0.10-2 (2022-12-01) ppc64le GNU/Linux
> $ ls -l /sys/kernel/bpf/
> ls: cannot access '/sys/kernel/bpf/': No such file or directory
> $ grep CONFIG_DEBUG_INFO_BTF /boot/config-6.0.0-5-powerpc64le
> # CONFIG_DEBUG_INFO_BTF is not set
>
> And in the latest powerpc64le kernel:
>
> $ grep CONFIG_DEBUG_INFO_BTF /boot/config-6.1.0-5-powerpc64le
> # CONFIG_DEBUG_INFO_BTF is not set
>
> Debian Testing arm64, not quite the latest kernel:
>
> $ uname -a
> Linux oak 6.1.0-5-arm64 #1 SMP Debian 6.1.12-1 (2023-02-15) aarch64 GNU/Linux
> $ ls -l /sys/kernel/bpf/
> ls: cannot access '/sys/kernel/bpf/': No such file or directory
> $ grep CONFIG_DEBUG_INFO_BTF /boot/config-6.1.0-5-arm64
> CONFIG_DEBUG_INFO_BTF=y
> CONFIG_DEBUG_INFO_BTF_MODULES=y
The running kernel is 6.1.12-1, the .config is 6.1.0-5
> Debian Testing amd64, the latest kernel:
>
> $ uname -a
> Linux pine 6.1.0-6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.15-1 (2023-03-05) x86_64 GNU/Linux
> $ ls -l /sys/kernel/bpf/
> ls: cannot access '/sys/kernel/bpf/': No such file or directory
> $ grep CONFIG_DEBUG_INFO_BTF /boot/config-6.1.0-6-amd64
> CONFIG_DEBUG_INFO_BTF=y
> CONFIG_DEBUG_INFO_BTF_MODULES=y
Ditto, 6.1.15-1 != 6.1.0-6
>
> Debian Stable amd64, the latest kernel:
>
> $ uname -a
> Linux gimli 5.10.0-21-cloud-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux
> $ ls -l /sys/kernel/bpf/
> ls: cannot access '/sys/kernel/bpf/': No such file or directory
> $ grep CONFIG_DEBUG_INFO_BTF /boot/config-5.10.0-21-cloud-amd64
> CONFIG_DEBUG_INFO_BTF=y
Ditto, 5.10.162-1 != 5.10.0-21-cloud
Here:
[acme@quaco pahole]$ grep CONFIG_DEBUG_INFO_BTF /boot/config-`uname -r`
CONFIG_DEBUG_INFO_BTF=y
CONFIG_DEBUG_INFO_BTF_MODULES=y
[acme@quaco pahole]$ uname -r
6.1.18-100.fc36.x86_64
[acme@quaco pahole]$
[acme@quaco pahole]$ ls -la /sys/kernel/btf/vmlinux
-r--r--r--. 1 root root 5499812 Mar 20 17:45 /sys/kernel/btf/vmlinux
[acme@quaco pahole]$ ls -la /sys/kernel/btf/nfsv4
-r--r--r--. 1 root root 319948 Mar 28 16:46 /sys/kernel/btf/nfsv4
[acme@quaco pahole]$ lsmod | grep -w nfsv4
nfsv4 1085440 1
dns_resolver 16384 1 nfsv4
nfs 532480 2 nfsv4
sunrpc 704512 26 nfsd,rpcrdma,nfsv4,auth_rpcgss,lockd,rpcsec_gss_krb5,nfs_acl,nfs
[acme@quaco pahole]$ ls -la /sys/kernel/btf/nfsd
-r--r--r--. 1 root root 596066 Mar 28 16:46 /sys/kernel/btf/nfsd
[acme@quaco pahole]$ ls -la /sys/kernel/btf/lockd
-r--r--r--. 1 root root 180234 Mar 28 16:46 /sys/kernel/btf/lockd
[acme@quaco pahole]$
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2023-03-28 19:47 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 22:50 linux-next: build failure after merge of the perf tree Stephen Rothwell
2023-03-16 23:11 ` Arnaldo Carvalho de Melo
2023-03-16 23:55 ` Stephen Rothwell
2023-03-17 3:23 ` Ian Rogers
2023-03-21 21:39 ` Stephen Rothwell
2023-03-22 18:37 ` Ian Rogers
2023-03-22 22:54 ` Stephen Rothwell
2023-03-23 13:27 ` Arnaldo Carvalho de Melo
2023-03-27 20:31 ` Ian Rogers
2023-03-28 1:33 ` Stephen Rothwell
2023-03-28 19:47 ` Arnaldo Carvalho de Melo [this message]
2023-03-28 23:06 ` Stephen Rothwell
2023-03-29 12:28 ` Arnaldo Carvalho de Melo
2023-04-03 5:15 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-03-26 23:22 Stephen Rothwell
2025-03-28 6:40 ` Namhyung Kim
2025-02-14 4:20 Stephen Rothwell
2025-01-09 23:05 Stephen Rothwell
2025-01-09 23:31 ` Charlie Jenkins
2025-01-10 14:01 ` Arnaldo Carvalho de Melo
2025-01-10 17:32 ` Arnaldo Carvalho de Melo
2025-01-10 18:59 ` Charlie Jenkins
2025-01-10 19:22 ` Charlie Jenkins
2024-10-10 23:23 Stephen Rothwell
2024-09-05 1:55 Stephen Rothwell
2024-04-01 22:41 Stephen Rothwell
2024-04-02 20:17 ` Arnaldo Carvalho de Melo
2024-04-12 15:22 ` Arnaldo Carvalho de Melo
2024-04-13 2:43 ` Stephen Rothwell
2024-03-21 21:41 Stephen Rothwell
2024-03-21 23:18 ` Arnaldo Carvalho de Melo
2024-03-21 23:19 ` Arnaldo Carvalho de Melo
2024-03-21 23:32 ` Stephen Rothwell
2024-03-22 2:13 ` Stephen Rothwell
2024-03-22 14:32 ` Arnaldo Carvalho de Melo
2024-03-21 23:36 ` Stephen Rothwell
2024-03-21 23:40 ` arnaldo.melo
2024-03-21 23:48 ` Arnaldo Carvalho de Melo
2024-02-21 23:06 Stephen Rothwell
2024-02-23 19:50 ` Arnaldo Carvalho de Melo
2024-02-06 23:40 Stephen Rothwell
2024-02-07 0:02 ` Ian Rogers
2023-10-24 23:26 Stephen Rothwell
2023-10-25 0:34 ` Namhyung Kim
2023-05-29 23:05 Stephen Rothwell
2023-05-30 2:16 ` Ian Rogers
2022-08-30 22:34 Stephen Rothwell
2022-09-01 5:11 ` Anshuman Khandual
2022-09-06 19:05 ` Stephen Rothwell
2022-09-07 2:31 ` Anshuman Khandual
2022-09-07 3:00 ` Stephen Rothwell
2022-09-07 4:22 ` Anshuman Khandual
2022-09-08 15:21 ` Arnaldo Carvalho de Melo
2022-07-20 23:05 Stephen Rothwell
2022-07-21 2:35 ` Ian Rogers
2022-07-21 3:55 ` Stephen Rothwell
2022-07-21 5:33 ` Ian Rogers
2022-01-05 22:19 Stephen Rothwell
2022-01-07 8:58 ` kajoljain
2022-01-11 21:45 ` Stephen Rothwell
2022-01-11 22:01 ` Arnaldo Carvalho de Melo
2022-01-12 5:30 ` kajoljain
2022-01-12 6:16 ` Stephen Rothwell
2022-01-14 12:03 ` Michael Ellerman
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=ZCNES6N7AkskjD0o@kernel.org \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).