From: Borislav Petkov <bp@alien8.de>
To: "NOMURA JUNICHI(野村 淳一)" <junichi.nomura@nec.com>,
"Michael Roth" <michael.roth@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>, "x86@kernel.org" <x86@kernel.org>
Subject: Re: [Regression v5.19-rc1] crash kexec fails to boot the 2nd kernel (Re: [PATCH v12 38/46] x86/sev: Add SEV-SNP feature detection/setup)
Date: Wed, 29 Jun 2022 10:20:27 +0200 [thread overview]
Message-ID: <YrwLS8qRDhjmeD5Z@zn.tnic> (raw)
In-Reply-To: <OSZPR01MB6953EEF3F8E63330547E031183BB9@OSZPR01MB6953.jpnprd01.prod.outlook.com>
On Wed, Jun 29, 2022 at 07:38:09AM +0000, NOMURA JUNICHI(野村 淳一) wrote:
> > If so, can you apply the below potential fix, and retry your original
> > reproducer?
>
> I tried your potential fix but it didn't work... The symptom was same
> as before.
I still think the proper fix is to not execute that cc blob code on
anything but AMD...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-06-29 8:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 0:44 [Regression v5.19-rc1] crash kexec fails to boot the 2nd kernel (Re: [PATCH v12 38/46] x86/sev: Add SEV-SNP feature detection/setup) NOMURA JUNICHI(野村 淳一)
2022-06-24 9:03 ` Borislav Petkov
2022-06-24 10:14 ` NOMURA JUNICHI(野村 淳一)
2022-06-29 0:41 ` Michael Roth
2022-06-29 7:38 ` NOMURA JUNICHI(野村 淳一)
2022-06-29 8:20 ` Borislav Petkov [this message]
2022-06-29 11:06 ` NOMURA JUNICHI(野村 淳一)
2022-06-29 13:52 ` Michael Roth
2022-06-29 15:35 ` Michael Roth
2022-06-29 13:54 ` Michael Roth
2022-06-30 8:25 ` NOMURA JUNICHI(野村 淳一)
2022-08-16 14:25 ` [Regression v5.19-rc1] kernel fails to boot, no console output " Jeremi Piotrowski
2022-08-16 15:06 ` Michael Roth
2022-08-17 8:40 ` Jeremi Piotrowski
2022-08-22 16:39 ` Michael Roth
2022-09-08 9:35 ` Jeremi Piotrowski
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=YrwLS8qRDhjmeD5Z@zn.tnic \
--to=bp@alien8.de \
--cc=junichi.nomura@nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.