From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Lindee <chris.lindee@gmail.com>
Cc: Borislav Petkov <bp@alien8.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: Wed, 13 Dec 2023 15:34:53 +0100 [thread overview]
Message-ID: <87bkaup3w2.ffs@tglx> (raw)
In-Reply-To: <CA+2tU5_TzDQO2U8SGDYhsVPR8iYh8Q8vTqv9+HUc7LN3cV=2Sg@mail.gmail.com>
On Tue, Dec 12 2023 at 13:11, Chris Lindee wrote:
> On Tue, Dec 12, 2023 at 8:34 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>> Can you please provide dmesg output from 6.7-rc4 with "cpuhp.parallel=0"
>> on the command line?
>
> Oops, I already upgraded to 6.7-rc5
> <https://koji.fedoraproject.org/koji/buildinfo?buildID=2332379>; let me
> know if you would prefer I downgrade.
Nah. That's fine.
> [ 0.002775] x2apic: enabled by BIOS, switching to x2apic ops
So BIOS has x2apic enabled, but ...
> [ 0.136888] smp: Bringing up secondary CPUs ...
> [ 0.136888] smpboot: x86: Booting SMP configuration:
> [ 0.136888] .... node #0, CPUs: #1
> [ 0.013471] x2apic enabled
this is really strange as it means that the APs do not come up with
X2APIC enabled. Oh well. BIOS creativity is unlimited...
> [ 0.137980] #2 #3
> [ 0.139937] smp: Brought up 1 node, 4 CPUs
Though that does not really explain why the parallel bringup goes south
as that is not really different from what the serialized bringup is
doing in terms of kicking the APs into life.
Can you try and add "ignore_loglevel earlyprintk=ttyS0,115200n8" to the
kernel command line and capture dmesg on the serial port when booting
with the parallel hotplug enabled?
Thanks,
tglx
next prev parent reply other threads:[~2023-12-13 14:35 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 ` [REGRESSION] x86/smpboot/64: System will not boot on v6.5, v6.7-rc4 Borislav Petkov
[not found] ` <CA+2tU585yW2z37NtYqjVe+ZMw+oU_vbS4X=Q=sAxME8GrPFDpg@mail.gmail.com>
2023-12-12 14:34 ` Thomas Gleixner
[not found] ` <CA+2tU5_TzDQO2U8SGDYhsVPR8iYh8Q8vTqv9+HUc7LN3cV=2Sg@mail.gmail.com>
2023-12-13 14:34 ` Thomas Gleixner [this message]
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=87bkaup3w2.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.