On Mon, 18 Oct 2021, Willy Tarreau wrote: > 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. OK, thanks for the suggestions. My impression is that there is a real performance problem in 5.11. The part I don't understand is why once I have booted that kernel, all of the kernels I make afterwards have the same performance characteristics. If I do git clean -dfx, then copy a fixed configuration to .config, and then use make olddefconfig, should anything about the currently running kernel have an impact on the kernel that is produced? I'll try simply rebooting the machine on each git bisect step. That should eliminate one more aspect of local state. thanks, julia
