From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Wolfgang Walter <linux@stwm.de>, stable@vger.kernel.org
Subject: Re: stable v6.6.24 regression: boot fails: bisected to "x86/mpparse: Register APIC address only once"
Date: Fri, 5 Apr 2024 13:34:44 +0200 [thread overview]
Message-ID: <2024040516-spill-uselessly-0a0e@gregkh> (raw)
In-Reply-To: <87y19s82ya.ffs@tglx>
On Fri, Apr 05, 2024 at 01:27:09PM +0200, Thomas Gleixner wrote:
> On Fri, Apr 05 2024 at 12:35, Wolfgang Walter wrote:
> > Am 2024-04-04 17:57, schrieb Greg Kroah-Hartman:
> >> Is this also an issue in 6.9-rc1 or newer or 6.8.3 or newer?
> >>
> > It is not an issue with 6.9-rc1. 6.9-rc1 just boots fine.
>
> Bah. That's my fault.
>
> So before the topology evaluation rework landed in the 6.9 merge window
> this eventual double registration was harmless and only happening for a
> particular set of AMD machines. The topo rework restructured the whole
> procedure and caused the new warnings to trigger.
>
> So the Fixes tag I added to that commit was pointing at the wrong place
> and this needs to be reverted from all pre 6.9 stable kernels.
Sure, will be glad to, but what git is is "this"? The original report
is gone from my thread here, sorry.
greg k-h
next prev parent reply other threads:[~2024-04-05 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 12:07 stable v6.6.24 regression: boot fails: bisected to "x86/mpparse: Register APIC address only once" Wolfgang Walter
2024-04-04 15:57 ` 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 [this message]
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=2024040516-spill-uselessly-0a0e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux@stwm.de \
--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