From: Mario Limonciello <mario.limonciello@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Lyude Paul <lyude@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Early boot regression from f0551af0213 ("x86/topology: Ignore non-present APIC IDs in a present package")
Date: Wed, 8 May 2024 17:09:32 -0500 [thread overview]
Message-ID: <23e2c13f-7ff9-4336-97ae-088ec4401edf@amd.com> (raw)
In-Reply-To: <87h6f8nfg7.ffs@tglx>
On 5/8/2024 16:47, Thomas Gleixner wrote:
> Mario!
>
> On Thu, May 02 2024 at 05:33, Mario Limonciello wrote:
>> On 4/25/2024 16:42, Thomas Gleixner wrote:
>>> Right, that's what we saw with the debug patch. The ACPI/MADT table
>>> is clearly bonkers. The effect of it is that it pretends that the system
>>> has 16 possible CPUs:
>>>
>>> [ 0.089381] CPU topo: Allowing 8 present CPUs plus 8 hotplug CPUs
>>>
>>> Which in turn changes the sizing of the per CPU data and affects some
>>> other details which depend on the number of possible CPUs.
>>
>> At least this aspect of this I suspect is caused by commit
>> fed8d8773b8ea68ad99d9eee8c8343bef9da2c2c.
>>
>> If you try reverting that I expect the "hotplug CPUs" disappear.
>
> That does not solve anything.
>
> The topology core already rejects those CPUs and accounts only for 8,
> which in turn causes the boot to fail as also demonstrated by limiting
> the number of possible CPUs to 8.
>
> There is some other problem with this broken BIOS/ACPI.
Something very commonly done in BIOSes on AMD systems is that the FADT
has "entries" for the maximum number of CPUs that can be present. For
example if the system can support up to 12 cores and you buy an 8 core
vs 12 core the BIOS will have the same number of entries (probably 24
considering SMT) either way. In the case of 8 cores only 16 would end
up populated.
Looking at Lyude's logs that system is from before ACPI 6.3 was even
introduced so that's why I was suggesting that reverting that commit
might help at least the kernel claiming that it saw a number of hotplug
CPUs.
But yes, I agree it probably won't help the overall issue that started
this thread.
prev parent reply other threads:[~2024-05-08 22:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 21:21 Lyude Paul
2024-04-18 8:27 ` Borislav Petkov
2024-04-18 17:20 ` Lyude Paul
2024-04-18 19:13 ` Thomas Gleixner
2024-04-19 5:37 ` Thomas Gleixner
2024-04-19 17:38 ` Lyude Paul
2024-04-19 22:15 ` Thomas Gleixner
2024-04-23 17:09 ` Thomas Gleixner
2024-04-24 20:56 ` Lyude Paul
2024-04-25 2:11 ` Thomas Gleixner
2024-04-25 15:56 ` Lyude Paul
2024-04-25 21:42 ` Thomas Gleixner
2024-05-02 10:33 ` Mario Limonciello
2024-05-08 8:38 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-08 10:30 ` Thomas Gleixner
2024-05-08 21:02 ` Lyude Paul
2024-05-08 23:21 ` Lyude Paul
2024-05-13 14:08 ` Thomas Gleixner
2024-05-13 23:18 ` Lyude Paul
2024-05-13 23:32 ` Lyude Paul
2024-05-14 8:25 ` Thomas Gleixner
2024-05-15 23:15 ` Lyude Paul
2024-05-16 13:38 ` Thomas Gleixner
2024-05-22 19:35 ` Lyude Paul
2024-05-22 22:12 ` Thomas Gleixner
2024-05-23 5:20 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-23 10:47 ` Thomas Gleixner
2024-05-28 22:43 ` Thomas Gleixner
2024-06-03 16:22 ` Lyude Paul
2024-06-05 23:15 ` Lyude Paul
2024-06-06 9:50 ` Thomas Gleixner
2024-05-09 19:22 ` Lyude Paul
2024-05-08 21:47 ` Thomas Gleixner
2024-05-08 22:09 ` Mario Limonciello [this message]
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=23e2c13f-7ff9-4336-97ae-088ec4401edf@amd.com \
--to=mario.limonciello@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--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
Powered by JetHome