linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David R <david@unsolicited.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Panic starting 6.2.x and later 6.1.x kernels
Date: Tue, 28 Mar 2023 16:06:41 +0100	[thread overview]
Message-ID: <57385475-c289-356f-d696-fc6decce1390@unsolicited.net> (raw)
In-Reply-To: <20230328142014.GCZCL3nkW5Qx5jhfsB@fat_crate.local>

On 28/03/2023 15:20, Borislav Petkov wrote:
> On Tue, Mar 28, 2023 at 12:02:57PM +0100, David R wrote:
>> After more investigation :
>>
>>      Revert "x86/acpi/boot: Do not register processors that cannot be onlined
>> for x2APIC"
>>
>>      This reverts commit ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b.
>>
>> Corrects the issue for me.
> Hmm, weird. That commit came up already yesterday. But in conjunction
> with qemu.
>
> Does this fix it per chance?
>
> https://lore.kernel.org/all/20230327191026.3454-2-eric.devolder@oracle.com/
>
> You'd need to revert the revert and apply this one ontop.
>
> Thx.
>
Yes, that patch fixes it also. By all means add my tested by:

Thanks
David

  reply	other threads:[~2023-03-28 15:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  6:43 Panic starting 6.2.x and later 6.1.x kernels David R
2023-03-27  7:49 ` Borislav Petkov
2023-03-27  8:13   ` David R
2023-03-27 13:49     ` Thomas Gleixner
2023-03-27 13:51       ` David R
2023-03-27 14:23       ` David R
2023-03-27 15:53       ` David R
2023-03-27 16:21         ` David R
2023-03-28 11:02     ` David R
2023-03-28 14:20       ` Borislav Petkov
2023-03-28 15:06         ` David R [this message]
2023-03-28 17:10           ` Borislav Petkov
2023-03-28 17:32             ` David R
2023-03-28 17:33               ` Borislav Petkov
     [not found]             ` <9ed16be4-051d-c20f-0410-b8a973c4c09e@disroot.org>
2023-03-29 10:39               ` Borislav Petkov
2023-03-29 16:14                 ` Borislav Petkov
2023-03-29 16:20                   ` David R
2023-03-29 17:51                     ` Limonciello, Mario
2023-03-29 19:03                       ` David R
2023-03-29 19:07                         ` Limonciello, Mario
     [not found]                           ` <a0ca1e4e-891c-273d-e2d8-eeb9fc4d0c77@unsolicited.net>
2023-03-29 19:17                             ` Limonciello, Mario
2023-03-29 19:20                               ` David R
2023-03-29 19:24                                 ` Limonciello, Mario
2023-03-29 19:31                                   ` David R
2023-03-30  9:33 ` [tip: x86/urgent] x86/ACPI/boot: Use FADT version to check support for online capable tip-bot2 for Mario Limonciello
2023-03-30 20:50 Panic starting 6.2.x and later 6.1.x kernels gabipr2023

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=57385475-c289-356f-d696-fc6decce1390@unsolicited.net \
    --to=david@unsolicited.net \
    --cc=bp@alien8.de \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).