From: "NOMURA JUNICHI(野村 淳一)" <junichi.nomura@nec.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "brijesh.singh@amd.com" <brijesh.singh@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"michael.roth@amd.com" <michael.roth@amd.com>,
"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: Fri, 24 Jun 2022 10:14:58 +0000 [thread overview]
Message-ID: <TYCPR01MB69489CB7170CFB42F0CBC70383B49@TYCPR01MB6948.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <YrV98fRJuN3ifQ1j@zn.tnic>
[-- Attachment #1.1: Type: text/plain, Size: 786 bytes --]
From: Borislav Petkov <bp@alien8.de>
> What system is this? Full dmesg and .config pls.
>
> How exactly are you launching the kexec kernel, etc, etc?
dmesg, kernel config and a script to load kexec is attached.
I could reproduce the problem as followings:
# ./kexec-p-noinitrd.sh
# cat /sys/kernel/kexec_crash_loaded
1
# echo c > /proc/sysrq-trigger
If the problem reproduces, the system stops or resets just after
showing a call trace of sysrq-panic on console.
On kernels without problem, it should show boot messages from
the 2nd kernel after the sysrq-panic call trace.
When I use "--noefi" option of kexec, the problem didn't occur.
So I think you need EFI-based system to reproduce the problem.
--
Jun'ichi Nomura, NEC Corporation / NEC Solution Innovators, Ltd.
[-- Attachment #1.2: repro.tgz --]
[-- Type: application/x-compressed, Size: 81948 bytes --]
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5766 bytes --]
next prev parent reply other threads:[~2022-06-24 10:15 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(野村 淳一) [this message]
2022-06-29 0:41 ` Michael Roth
2022-06-29 7:38 ` NOMURA JUNICHI(野村 淳一)
2022-06-29 8:20 ` Borislav Petkov
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=TYCPR01MB69489CB7170CFB42F0CBC70383B49@TYCPR01MB6948.jpnprd01.prod.outlook.com \
--to=junichi.nomura@nec.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.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.