From: Domenico Andreoli <cavok@debian.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Domenico Andreoli <cavok@debian.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
debian-kernel@lists.debian.org, debian-powerpc@lists.debian.org,
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: Sat, 20 Jul 2024 09:47:59 +0200 [thread overview]
Message-ID: <Zptrr4YbzLQ7rk4b@macchia.lan> (raw)
In-Reply-To: <9bbcd88a1a0ae844d546468a3d68d3d60b9e3b13.camel@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
On Sat, Jul 20, 2024 at 09:16:24AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Domenico,
Hi!
> On Fri, 2024-07-19 at 23:20 +0200, Domenico Andreoli wrote:
> > > > 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?
> >
> > I don't have access to the build host (blaauw2) and I've some doubts
> > it would still have that file.
> >
> > Maybe our kernel team and powerpc porters have suggestions?
>
> I have root access to all powerpc/ppc64 machines (buildds and porterbox).
>
> I'm cleaning up the porterbox now, disk is quite full, then you can try
> to build the kernel package on perotto.debian.net or I can try it myself.
>
> I have seen the bug myself and I wanted to debug it, but the attempt was
> foiled by the fact that the disk on perotto is full (again).
>
> Will take care of it and let you know when it's (some hours).
That's great, thank you.
>
> Adrian
>
> --
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer
> `. `' Physicist
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--
rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-20 7:48 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
2024-07-19 21:20 ` Domenico Andreoli
2024-07-20 7:16 ` John Paul Adrian Glaubitz
2024-07-20 7:47 ` Domenico Andreoli [this message]
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=Zptrr4YbzLQ7rk4b@macchia.lan \
--to=cavok@debian.org \
--cc=1076564@bugs.debian.org \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=debian-powerpc@lists.debian.org \
--cc=dwarves@vger.kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--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 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.