Control: clone -1 -2 Control: reassign -2 src:binutils Control: found -2 binutils/2.42.50.20240618-1
I'm cloning this to src:binutils as the problem is likely either there or in gcc; as Johannes stated below, the newer gcc requires the new binutils. If it's gcc, please reassign there. CC-ed debian-arm@ to also reach the ARM64 porters. On Sun, Jun 23, 2024 at 11:44:05AM +0200, Johannes Schauer Marin Rodrigues wrote: > [..] Compiling the > same kernel version 6.8.12 in *unstable* within a more recent build > environment > results in a vmlinuz that just prints on boot: > > Starting kernel ... > > And then nothing else. Since neither the linux sources in debian unstable > changed, nor our patch stack changed between these rebuilds, the culprit is > likely in the build environment. [..] > [..] We also observed how the good vmlinuz has a size of 31M and > the bad vmlinuz a size of only 26M. > This is with the same sources, just different build chroot environment. An > old-enough build environment can be constructed using snapshot.d.o. > One of the differences in the build environment between good and bad builds is > binutils-arm-linux-gnueabihf with version 2.42-4 in the good environment and > version 2.42.50.20240618-1 in the bad environment. To test whether this indeed > triggers the problem, we tested building our kernel with current unstable but > with binutils (= 2.42-4) and gcc-13 (= 13.2.0-25). We also have to choose an > older gcc from snapshot.d.o because recent gcc-13 requires recent binutils. > This makes the kernel work again. > So, given that the problem affects linux in unstable *if* built with a more > recent build environment, the problem might not be in src:linux but elsewhere > (maybe binutils or gcc-13). I'm still filing it here as I lack the skills to > investigate this problem further. Since the issue shows up with qemu, I'm sure > that you can get to the bottom of it and can re-assign this bug to the package > to which it belongs. I think this also means rebuilding an existing kernel in unstable or testing will also break. Chris
