From: Borislav Petkov <bp@alien8.de>
To: Chris Lindee <chris.lindee@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
regressions@lists.linux.dev, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ashok Raj <ashok.raj@intel.com>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [REGRESSION] x86/smpboot/64: System will not boot on v6.5, v6.7-rc4
Date: Sun, 10 Dec 2023 12:05:18 +0100 [thread overview]
Message-ID: <20231210110518.GAZXWbbn9+ZNF5kwQV@fat_crate.local> (raw)
In-Reply-To: <CA+2tU59853R49EaU_tyvOZuOTDdcU0RshGyydccp9R1NX9bEeQ@mail.gmail.com>
On Sat, Dec 09, 2023 at 09:31:48PM -0600, Chris Lindee wrote:
> My Dell-EMC PowerEdge T340 server worked with v6.4.15, but it will not
> start with v6.5.x - it won't even display dmesg events during boot. I
> reproduced the issue on v6.7-rc4 and bisected the first problematic commit
> to:
>
> 0c7ffa32dbd6 x86/smpboot/64: Implement arch_cpuhp_init_parallel_bringup()
> and enable it
I presume booting with "cpuhp.parallel=0" on the kernel cmdline fixes
it?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next parent reply other threads:[~2023-12-10 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+2tU59853R49EaU_tyvOZuOTDdcU0RshGyydccp9R1NX9bEeQ@mail.gmail.com>
2023-12-10 11:05 ` Borislav Petkov [this message]
[not found] ` <CA+2tU585yW2z37NtYqjVe+ZMw+oU_vbS4X=Q=sAxME8GrPFDpg@mail.gmail.com>
2023-12-12 14:34 ` [REGRESSION] x86/smpboot/64: System will not boot on v6.5, v6.7-rc4 Thomas Gleixner
[not found] ` <CA+2tU5_TzDQO2U8SGDYhsVPR8iYh8Q8vTqv9+HUc7LN3cV=2Sg@mail.gmail.com>
2023-12-13 14:34 ` Thomas Gleixner
2023-12-13 21:08 ` Thomas Gleixner
[not found] ` <CA+2tU5-RoR8qCGRdsMH0wo5n8v4fV8A_H5yT+mZadsF7E+QkWg@mail.gmail.com>
[not found] ` <CA+2tU5-18YQSpFzgUKyeZdJXe0Rs0GxtYY2s5QjznzTucJKCiQ@mail.gmail.com>
2023-12-14 7:04 ` Thomas Gleixner
[not found] ` <CA+2tU596G+auWJ2MzYFJ3bv=Y4zP2NSrdtak7SdF9SH6Ht_dzg@mail.gmail.com>
2023-12-15 8:58 ` [PATCH] x86/smpboot/64: Handle X2APIC BIOS inconsistency gracefully Thomas Gleixner
2023-12-15 15:41 ` Ashok Raj
[not found] ` <CA+2tU5_hD-atkp9UcCJnL6TMneSOBxL87=ppvrQ1ugUn_0-7NA@mail.gmail.com>
2023-12-15 18:35 ` Borislav Petkov
2023-12-12 15:32 ` [REGRESSION] x86/smpboot/64: System will not boot on v6.5, v6.7-rc4 Linux regression tracking #adding (Thorsten Leemhuis)
2024-03-11 19:47 ` Guenter Roeck
2024-03-12 9:13 ` Thorsten Leemhuis
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=20231210110518.GAZXWbbn9+ZNF5kwQV@fat_crate.local \
--to=bp@alien8.de \
--cc=ashok.raj@intel.com \
--cc=chris.lindee@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).