[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYtNcnAEVs70eH2yP5UxRBsfrN2B1nKNcggGQ7FNMAJMmg@mail.gmail.com>
Date: Mon, 7 Apr 2025 20:47:12 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: open list <linux-kernel@...r.kernel.org>, clang-built-linux <llvm@...ts.linux.dev>,
Linux Regressions <regressions@...ts.linux.dev>, lkft-triage@...ts.linaro.org
Cc: Nathan Chancellor <nathan@...nel.org>, Dan Carpenter <dan.carpenter@...aro.org>,
Arnd Bergmann <arnd@...db.de>, Anders Roxell <anders.roxell@...aro.org>,
Ard Biesheuvel <ardb@...nel.org>, Ingo Molnar <mingo@...nel.org>, dwmw@...zon.co.uk,
"H. Peter Anvin" <hpa@...or.com>, Kees Cook <keescook@...omium.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: next-20250407: qemu_x86_64 clang-20, clang-nightly no console log
but gcc-13 boot pass
On Mon, 7 Apr 2025 at 17:15, Naresh Kamboju <naresh.kamboju@...aro.org> 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@...aro.org>
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@mail.gmail.com/
- Naresh
Powered by blists - more mailing lists