From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Aaron Lu <aaron.lu@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Borislav Petkov (AMD) <bp@alien8.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: kexec reboot failed due to commit 75d090fd167ac
Date: Tue, 29 Aug 2023 19:14:59 +0700 [thread overview]
Message-ID: <ZO3hQ0rbr8QuUjVI@debian.me> (raw)
In-Reply-To: <20230829114816.GA508985@ziqianlu-dell>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Tue, Aug 29, 2023 at 07:48:16PM +0800, Aaron Lu wrote:
> Hi Kirill,
>
> Ever since v6.5-rc1, I found that I can not use kexec to reboot an Intel
> SPR test machine. With git bisect, the first bad commit is 75d090fd167ac
> ("x86/tdx: Add unaccepted memory support").
>
> I have no idea why a tdx change would affect it, I'm not doing anything
> related to tdx.
>
> Any ideas?
>
> The kernel config is attached, let me know if you need any other info.
Can you provide system logs (e.g. journalctl output) when attempting to
reboot?
Anyway, thanks for the regression report. I'm adding it to regzbot:
#regzbot ^introduced: 75d090fd167aca
#regzbot title: unable to reboot with kexec due to TDX unaccepted memory support
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-29 12:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 11:48 kexec reboot failed due to commit 75d090fd167ac Aaron Lu
2023-08-29 12:14 ` Bagas Sanjaya [this message]
2023-08-29 12:51 ` Aaron Lu
2023-08-29 12:59 ` Kirill A. Shutemov
2023-08-29 14:04 ` Aaron Lu
2023-09-07 13:14 ` Kirill A. Shutemov
2023-09-08 6:02 ` Aaron Lu
2023-09-08 12:32 ` Kirill A. Shutemov
2023-09-08 15:58 ` Kees Cook
2023-09-08 16:17 ` Ard Biesheuvel
2023-09-09 11:32 ` Kirill A. Shutemov
2023-09-11 14:56 ` Dave Young
2023-09-11 14:57 ` Kirill A. Shutemov
2023-09-11 15:33 ` Tom Lendacky
2023-09-11 15:53 ` Kirill A. Shutemov
2023-09-11 17:13 ` Tom Lendacky
2023-09-13 14:24 ` Kirill A. Shutemov
2023-09-21 9:54 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-21 16:03 ` Kirill A. Shutemov
2023-09-22 10:12 ` Linux regression tracking #update (Thorsten Leemhuis)
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=ZO3hQ0rbr8QuUjVI@debian.me \
--to=bagasdotme@gmail.com \
--cc=aaron.lu@intel.com \
--cc=bp@alien8.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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