From: Borislav Petkov <bp@alien8.de>
To: Guy Durrieu <guy.durrieu@cegetel.net>,
Kishon Vijay Abraham I <kvijayab@amd.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Santosh Shukla <santosh.shukla@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Borislav Petkov <bpetkov@amd.com>, Leo Duran <leo.duran@amd.com>,
1033732@bugs.debian.org
Subject: Re: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic
Date: Sun, 02 Apr 2023 12:57:29 +0200 [thread overview]
Message-ID: <D2229CD1-CD5F-49E9-A0F5-BAB3940B6BFB@alien8.de> (raw)
In-Reply-To: <c02a2a2f-2b40-e13e-ac40-e5d19a66b5ba@cegetel.net>
On April 2, 2023 12:41:46 PM GMT+02:00, Guy Durrieu <guy.durrieu@cegetel.net> wrote:
>My system worked fine with kernel 6.1.15, but stopped booting after
>upgrading to 6.1.20 and resulted in a kernel panic:
Does this fix it:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent
Thx.
--
Sent from a small device: formatting sucks and brevity is inevitable.
next prev parent reply other threads:[~2023-04-02 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 4:10 Kishon Vijay Abraham I
2023-01-05 17:09 ` Rafael J. Wysocki
2023-01-05 22:22 ` Borislav Petkov
2023-01-10 13:03 ` Rafael J. Wysocki
2023-01-10 18:23 ` Borislav Petkov
2023-01-06 0:57 ` Zhang, Rui
2023-01-10 18:41 ` [tip: x86/boot] x86/acpi/boot: Do not register processors that cannot be onlined for x2APIC tip-bot2 for Kishon Vijay Abraham I
2023-04-02 10:41 ` [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic Guy Durrieu
2023-04-02 10:57 ` Borislav Petkov [this message]
2023-04-02 13:13 ` Guy Durrieu
2023-04-02 15:18 ` Borislav Petkov
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=D2229CD1-CD5F-49E9-A0F5-BAB3940B6BFB@alien8.de \
--to=bp@alien8.de \
--cc=1033732@bugs.debian.org \
--cc=bpetkov@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=guy.durrieu@cegetel.net \
--cc=hpa@zytor.com \
--cc=kvijayab@amd.com \
--cc=len.brown@intel.com \
--cc=leo.duran@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=santosh.shukla@amd.com \
--cc=suravee.suthikulpanit@amd.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
all inboxes | Powered by JetHome®