From: gabipr2023@proton.me
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kishon Vijay Abraham I <kvijayab@amd.com>,
David R <david@unsolicited.net>, Borislav Petkov <bp@alien8.de>,
eric.devolder@oracle.com
Subject: Re: Panic starting 6.2.x and later 6.1.x kernels
Date: Thu, 30 Mar 2023 20:50:36 +0000 [thread overview]
Message-ID: <788384b22962ff2fc716bd7cc82d08071bf440d1.camel@proton.me> (raw)
On Wed, 2023-03-29 at 14:17 -0500, Limonciello, Mario wrote:
>
>
> You mean specifically this change:
> https://lore.kernel.org/all/20230327191026.3454-2-eric.devolder@oracle.com/
>
> Yes; I suppose that still makes sense.
>
Just tried this patch on 6.3rc4 and it boots correctly for me with just
this.
(Offtopic but also my name is Gabriela, a typo from my part lol. And
this is another email since disroot is blocked my lkml)
next reply other threads:[~2023-03-30 20:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 20:50 gabipr2023 [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 6:43 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
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
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=788384b22962ff2fc716bd7cc82d08071bf440d1.camel@proton.me \
--to=gabipr2023@proton.me \
--cc=bp@alien8.de \
--cc=david@unsolicited.net \
--cc=eric.devolder@oracle.com \
--cc=kvijayab@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--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
all inboxes | Powered by JetHome®