From: Peter Zijlstra <peterz@infradead.org>
To: "Erhard F." <erhard_f@mailbox.org>
Cc: sandipan.das@amd.com, linux-kernel@vger.kernel.org
Subject: Re: [bisected] clang 15 built kernel fails to boot, stuck at "Loading Linux 6.1.1 ...", gcc 12 built kernel with same config boots fine
Date: Thu, 19 Jan 2023 14:56:07 +0100 [thread overview]
Message-ID: <Y8lL95T93g5xK+mu@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230119022303.177052e4@yea>
On Thu, Jan 19, 2023 at 02:23:03AM +0100, Erhard F. wrote:
> Hi!
>
> I did a kernel bisect for an issue I originally posted on https://github.com/ClangBuiltLinux/linux/issues/1774
>
> It is about kernel 6.1.x not booting on my machines when built with clang. A gcc built kernel with the same config just works fine. Turns out kernel v6.2-rc4 and earlier v6.2-rc are still affected.
>
> I did a kernel bisect which revealed this commit:
>
> # git bisect bad
> 706460a96fc654e80b6bed1f562b00d2ce9f2f4d is the first bad commit
> commit 706460a96fc654e80b6bed1f562b00d2ce9f2f4d
> Author: Sandipan Das <sandipan.das@amd.com>
> Date: Thu Aug 11 17:59:51 2022 +0530
>
> perf/x86/amd/core: Add generic branch record interfaces
>
> AMD processors that are capable of recording branches support either Branch
> Sampling (BRS) or Last Branch Record (LBR). In preparation for adding Last
> Branch Record Extension Version 2 (LbrExtV2) support, introduce new static
> calls which act as gateways to call into the feature-dependent functions
> based on what is available on the processor.
>
> Signed-off-by: Sandipan Das <sandipan.das@amd.com>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Link: https://lore.kernel.org/r/b75dbc32663cb395f0d701167e952c6a6b0445a3.1660211399.git.sandipan.das@amd.com
>
> arch/x86/events/amd/core.c | 34 ++++++++++++++++++++++------------
> 1 file changed, 22 insertions(+), 12 deletions(-)
Using: v6.2-rc4-67-g7287904c8771
I have an AMD Interlagos and after bringing it back to live/up-to-date I
can't seem to even boot your .config in qemu/kvm irrespective of
GCC/Clang.
When I build defconfig+kvm_guest.config both GCC-12 and clang-15 boot
just fine in qemu/kvm.
next prev parent reply other threads:[~2023-01-19 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 1:23 Erhard F.
2023-01-19 13:56 ` Peter Zijlstra [this message]
2023-01-19 15:18 ` Peter Zijlstra
2023-01-20 5:50 ` Sandipan Das
2023-01-20 10:27 ` Peter Zijlstra
2023-01-20 11:16 ` Peter Zijlstra
2023-01-20 11:49 ` Erhard F.
2023-01-20 14:57 ` Peter Zijlstra
2023-01-20 15:20 ` Erhard F.
2023-01-20 16:13 ` Peter Zijlstra
2023-01-20 15:32 ` Peter Zijlstra
2023-01-22 8:46 ` Masami Hiramatsu
2023-01-19 14:44 ` Linux kernel regression tracking (#adding)
2023-01-26 11:47 ` Linux kernel regression tracking (#update)
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=Y8lL95T93g5xK+mu@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=erhard_f@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandipan.das@amd.com \
/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
all inboxes | Powered by JetHome®