From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Domenico Andreoli <cavok@debian.org>
Cc: Alan Maguire <alan.maguire@oracle.com>,
Jiri Olsa <jolsa@kernel.org>, Ben Hutchings <ben@decadent.org.uk>,
1076564@bugs.debian.org, dwarves@vger.kernel.org
Subject: Re: Bug#1076564: pahole BTF processing seems flaky on powerpc
Date: Fri, 19 Jul 2024 16:13:00 -0300 [thread overview]
Message-ID: <Zpq6vEB3G1UlAeGR@x1> (raw)
In-Reply-To: <ZpoNZHIYuERg49N1@localhost>
Adding Alan and Jiri to the CC list.
On Fri, Jul 19, 2024 at 08:53:24AM +0200, Domenico Andreoli wrote:
> Hi Arnaldo,
>
> On Thu, Jul 18, 2024 at 11:56:09PM +0200, Ben Hutchings wrote:
> > Package: pahole
> > Version: 1.27-1
> > Severity: normal
> > X-Debbugs-Cc: debian-kernel@lists.debian.org
> >
> > Several kernel builds on powerpc have failed recently:
> >
> > 6.8.12-1: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpc&ver=6.8.12-1&stamp=1717234422&raw=1
> > 6.9.9-1: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpc&ver=6.9.9-1&stamp=1720906547&raw=1
> > 6.10-1~exp1: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpc&ver=6.10-1%7Eexp1&stamp=1721287862&raw=1
> >
> > Note, these log files are up to 270 MB in size and should be
> > downloaded; at least Firefox becomes unresponsive when trying to
> > display them.
> >
> > For each of these, the failure seems to start with an error from
> > pahole such as:
> >
> > [102044] ARRAY (anon) type_id=99491 index_type_id=14 nr_elems=12 Error emitting BTF type
> > Encountered error while encoding BTF.
>
> Does the above error ring any bell?
Nope
> Is there anything I can do to help?
From the 6.10-1~exp1:
https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpc&ver=6.10-1%7Eexp1&stamp=1721287862&raw=1
file:
+ LLVM_OBJCOPY=powerpc-linux-gnu-objcopy pahole -J -j --btf_features=encode_force,var,float,enum64,decl_tag,type_tag,optimized_func,consistent_func --lang_exclude=rust .tmp_vmlinux.btf
Can I have access to that .tmp_vmlinux.btf file so that I can try to
reproduce it here?
- Arnaldo
> >
> > This does *not* happen consistently. Compare these successful
> > builds:
> >
> > 6.8.12-1: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpc&ver=6.8.12-1&stamp=1717278092&raw=1
> > - This same version failed to build on the first try.
> > 6.9.7-1: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpc&ver=6.9.7-1&stamp=1719538806&raw=1
> > - Earlier and later 6.9.x versions failed to build.
> >
> > Both pahole versions 1.26-1 and 1.27-1 have been used in both
> > successful and failing builds.
> >
> > Ben.
> >
> > -- System Information:
> > Debian Release: trixie/sid
> > APT prefers unstable-debug
> > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable-updates'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 6.9.9-amd64 (SMP w/12 CPU threads; PREEMPT)
> > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages pahole depends on:
> > ii libbpf1 1:1.4.3-1
> > ii libc6 2.39-4
> > ii libdw1t64 0.191-2
> > ii libelf1t64 0.191-2
> > ii zlib1g 1:1.3.dfsg+really1.3.1-1
> >
> > pahole recommends no packages.
> >
> > pahole suggests no packages.
> >
> > -- debconf-show failed
>
> --
> rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
> ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
next prev parent reply other threads:[~2024-07-19 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172133976964.70930.13662511677581571913.reportbug@deadeye.wl.decadent.org.uk>
2024-07-19 6:53 ` Bug#1076564: pahole BTF processing seems flaky on powerpc Domenico Andreoli
2024-07-19 9:08 ` Domenico Andreoli
2024-07-19 19:13 ` Arnaldo Carvalho de Melo [this message]
2024-07-19 21:20 ` Domenico Andreoli
2024-07-20 7:16 ` John Paul Adrian Glaubitz
2024-07-20 7:47 ` Domenico Andreoli
2024-07-20 19:17 ` Ben Hutchings
2024-07-20 19:45 ` John Paul Adrian Glaubitz
2024-07-21 22:07 ` Ben Hutchings
2024-07-22 4:57 ` John Paul Adrian Glaubitz
2024-07-24 10:04 ` Alan Maguire
2024-07-24 16:29 ` Arnaldo Carvalho de Melo
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=Zpq6vEB3G1UlAeGR@x1 \
--to=acme@kernel.org \
--cc=1076564@bugs.debian.org \
--cc=alan.maguire@oracle.com \
--cc=ben@decadent.org.uk \
--cc=cavok@debian.org \
--cc=dwarves@vger.kernel.org \
--cc=jolsa@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