From: Thomas Gleixner <tglx@linutronix.de>
To: Christian Heusel <christian@heusel.eu>, Borislav Petkov <bp@alien8.de>
Cc: regressions@lists.linux.dev, x86@kernel.org, rob@durendal.co.uk,
Joerg Roedel <joro@8bytes.org>
Subject: Re: [REGRESSION][BISECTED] Early boot hangs since f0551af02130
Date: Fri, 26 Jul 2024 12:50:20 +0200 [thread overview]
Message-ID: <87a5i4whoz.ffs@tglx> (raw)
In-Reply-To: <12df8b45-6100-4c8b-b82a-a6a75bed2e05@heusel.eu>
On Fri, Jul 26 2024 at 00:01, Christian Heusel wrote:
> Sorry for causing some confusion on that part and I hope the above
> outputs help with debugging this issue!
Not really. The issue is completely unclear and nothing makes any sense
here.
The only difference is the resulting number of possible CPUs.
[ 0.026516] CPU topo: Allowing 4 present CPUs plus 12 hotplug CPUs
versus:
[ 0.025251] CPU topo: Allowing 4 present CPUs plus 0 hotplug CPUs
which really should not make any difference because the 1300X has only 4
CPUs.
So the bisected commit is the messenger for some other problem
presumably in the IOMMU area which is just papered over when there are
12 possible hotplug CPUs enumerated.
So in theory the same problem should happen with a pre 6.9 kernel and
'nr_cpus=4' on the kernel command line. Can you please verify?
Another data point to be evaluated is whether booting the unmodified
6.10+ kernel with 'nointremap' instead of 'iommu=off' on the command
line makes the machine boot as well.
Thanks,
tglx
next prev parent reply other threads:[~2024-07-26 10:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 13:11 [REGRESSION][BISECTED] Early boot hangs since f0551af02130 Christian Heusel
2024-07-23 11:42 ` Christian Heusel
2024-07-23 12:02 ` Borislav Petkov
2024-07-23 22:08 ` Christian Heusel
2024-07-25 10:50 ` Borislav Petkov
2024-07-25 22:01 ` Christian Heusel
2024-07-26 10:50 ` Thomas Gleixner [this message]
2024-07-26 10:57 ` Borislav Petkov
2024-07-26 21:18 ` Rob
2024-07-26 22:40 ` Rob
2024-07-27 6:40 ` Borislav Petkov
2024-07-27 7:41 ` Thomas Gleixner
2024-07-27 12:56 ` Rob
2024-07-27 15:26 ` Thomas Gleixner
2024-07-28 11:06 ` [PATCH] x86/apic: Remove logical destination mode for 64-bit Thomas Gleixner
2024-07-28 16:51 ` Rob
2024-08-09 9:37 ` Christian Heusel
2024-08-09 12:18 ` Thomas Gleixner
2024-09-05 13:28 ` Christian Heusel
2024-09-05 14:04 ` Borislav Petkov
2024-09-06 8:34 ` Linux regression tracking (Thorsten Leemhuis)
2024-09-06 13:59 ` Thomas Gleixner
2024-07-29 7:36 ` Borislav Petkov
2024-08-09 12:45 ` [tip: x86/apic] " tip-bot2 for Thomas Gleixner
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=87a5i4whoz.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=christian@heusel.eu \
--cc=joro@8bytes.org \
--cc=regressions@lists.linux.dev \
--cc=rob@durendal.co.uk \
--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.