Re: next-20250407: qemu_x86_64 clang-20, clang-nightly no console log but gcc-13 boot pass

From: Ingo Molnar
Date: Mon Apr 07 2025 - 13:53:34 EST



* Ard Biesheuvel <ardb@xxxxxxxxxx> wrote:

> On Mon, 7 Apr 2025 at 18:17, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote:
> >
> > On Mon, 7 Apr 2025 at 17:15, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote:
> > >
> > > Regressions on qemu-x86_64 with clang-20 and clang-nightly on the
> > > Linux next-20250407 and no console output.
> > >
> > > The gcc-13 builds boot pass on qemu-x86_64.
> > >
> > > First seen on the next-20250407.
> > > Bad: next-20250407
> > > Good:next-20250404
> > >
> > > * qemu-x86_64, boot
> > > - boot/clang-20-lkftconfig
> > > - boot/clang-20-lkftconfig-compat
> > > - boot/clang-nightly-lkftconfig
> > >
> > > Regression Analysis:
> > > - New regression? Yes
> > > - Reproducibility? Yes
> > >
> > > Boot regression: qemu_x86_64 clang-20, clang-nightly no console log
> > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx>
> >
> > Anders bisected this and found,
> > # first bad commit:
> > [cc34e658c6db493c1524077e95b42d478de58f2b]
> > x86/boot: Move the early GDT/IDT setup code into startup/
> >
> > Lore report link,
> > - https://lore.kernel.org/all/CA+G9fYt4VVa3kUDR+ze05xM+fRmMBVfbBTsypUq5oOpAfuzjfg@xxxxxxxxxxxxxx/
> >
>
> Thanks for the report. I'll look into this.

I've zapped cc34e658c6db from tip:x86/boot for the time being.

I have the same request as for the other patches applies, please split
it up into ~3 patches for better bisectability and ease of review:

- first the mechanic movement of code, with very few changes (if the
result builds & boots),

- then drop the RIP_REL_REF() uses in the second patch,

- and drop __head annotations in the third patch.

Thanks,

Ingo