From: Wolfgang Walter <linux@stwm.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, stable@vger.kernel.org
Subject: stable v6.6.24 regression: boot fails: bisected to "x86/mpparse: Register APIC address only once"
Date: Thu, 04 Apr 2024 14:07:11 +0200 [thread overview]
Message-ID: <23da7f59519df267035b204622d32770@stwm.de> (raw)
Hello,
after upgrading to v6.6.24 from v6.6.23 some old boxes (i686; Intel
Celeron M) stop to boot:
They hang after:
Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel (entry_offset: 0x00000000).
After some minutes they reboot.
I bisected this down to
commit bebb5af001dc6cb4f505bb21c4d5e2efbdc112e2
Author: Thomas Gleixner <tglx@linutronix.de>
Date: Fri Mar 22 19:56:39 2024 +0100
x86/mpparse: Register APIC address only once
[ Upstream commit f2208aa12c27bfada3c15c550c03ca81d42dcac2 ]
The APIC address is registered twice. First during the early
detection and
afterwards when actually scanning the table for APIC IDs. The APIC
and
topology core warn about the second attempt.
Restrict it to the early detection call.
Fixes: 81287ad65da5 ("x86/apic: Sanitize APIC address setup")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Link:
https://lore.kernel.org/r/20240322185305.297774848@linutronix.de
Signed-off-by: Sasha Levin <sashal@kernel.org>
Reverting this commit in v6.6.24 solves the problem.
Regards,
--
Wolfgang Walter
Studierendenwerk München Oberbayern
Anstalt des öffentlichen Rechts
next reply other threads:[~2024-04-04 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 12:07 Wolfgang Walter [this message]
2024-04-04 15:57 ` stable v6.6.24 regression: boot fails: bisected to "x86/mpparse: Register APIC address only once" Greg Kroah-Hartman
2024-04-05 9:33 ` Thomas Gleixner
2024-04-05 9:55 ` Wolfgang Walter
2024-04-05 10:51 ` Wolfgang Walter
2024-04-05 10:35 ` Wolfgang Walter
2024-04-05 11:27 ` Thomas Gleixner
2024-04-05 11:34 ` Greg Kroah-Hartman
2024-04-05 14:55 ` Thomas Gleixner
2024-04-08 10:45 ` Greg Kroah-Hartman
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=23da7f59519df267035b204622d32770@stwm.de \
--to=linux@stwm.de \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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