From: Willy Tarreau <w@1wt.eu>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org
Subject: Re: build reproducibility
Date: Mon, 18 Oct 2021 04:40:07 +0200 [thread overview]
Message-ID: <20211018024007.GA14455@1wt.eu> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110172041010.4761@hadrien>
Hello Julia,
On Sun, Oct 17, 2021 at 08:42:31PM +0200, Julia Lawall wrote:
> On Sun, 17 Oct 2021, Randy Dunlap wrote:
> > My "guess" is that this has something to do with the build
> > reusing some current file(s) that need to be rebuilt.
> > I.e., adding a "make clean" or "make proper" might be needed.
>
> This was my guess too. But I have the git clean -dfx. I did a comparison
> with make distclean and this does a little more (mostly some files in
> tools).
Have you tried power-cycling the machine between boots, or just
rebooting on a working kernel before booting again on a faulty one ?
It could be possible that "something" changes a hardware setting that
the BIOS does not touch, leaving your machine in a different state
after you've booted the first problematic kernel. For example, it's
possible to set some CPU MSRs that affect the maximum CPU power, hence
its performance. Normally the BIOS should reset them, but for this it
must know about the one your kernel (or even userland) would set.
Hoping this helps,
Willy
next prev parent reply other threads:[~2021-10-18 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 18:12 build reproducibility Julia Lawall
2021-10-17 18:32 ` Randy Dunlap
2021-10-17 18:42 ` Julia Lawall
2021-10-18 2:26 ` Masahiro Yamada
2021-10-18 2:40 ` Willy Tarreau [this message]
2021-10-18 5:51 ` Julia Lawall
2021-10-18 5:59 ` Willy Tarreau
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=20211018024007.GA14455@1wt.eu \
--to=w@1wt.eu \
--cc=julia.lawall@inria.fr \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.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