From: Aaron Lu <aaron.lu@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Borislav Petkov <bp@alien8.de>,
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: Fri, 8 Sep 2023 14:02:30 +0800 [thread overview]
Message-ID: <20230908060230.GA283801@ziqianlu-dell> (raw)
In-Reply-To: <20230907131409.masxz42ik6u456qp@box.shutemov.name>
On Thu, Sep 07, 2023 at 04:14:09PM +0300, Kirill A. Shutemov wrote:
> On Tue, Aug 29, 2023 at 10:04:51PM +0800, Aaron Lu wrote:
> > > Could you show dmesg of the first kernel before kexec?
> >
> > Attached.
> >
> > BTW, kexec is invoked like this:
> > kver=6.4.0-rc5-00009-g75d090fd167a
> > kdir=$HOME/kernels/$kver
> > sudo kexec -l $kdir/vmlinuz-$kver --initrd=$kdir/initramfs-$kver.img --append="root=UUID=4381321e-e01e-455a-9d46-5e8c4c5b2d02 ro net.ifnames=0 acpi_rsdp=0x728e8014 no_hash_pointers sched_verbose selinux=0"
>
> I don't understand why it happens.
>
> Could you check if this patch changes anything:
>
> diff --git a/arch/x86/boot/compressed/misc.c b/arch/x86/boot/compressed/misc.c
> index 94b7abcf624b..172c476ff6f3 100644
> --- a/arch/x86/boot/compressed/misc.c
> +++ b/arch/x86/boot/compressed/misc.c
> @@ -456,10 +456,12 @@ asmlinkage __visible void *extract_kernel(void *rmode, memptr heap,
>
> debug_putstr("\nDecompressing Linux... ");
>
> +#if 0
> if (init_unaccepted_memory()) {
> debug_putstr("Accepting memory... ");
> accept_memory(__pa(output), __pa(output) + needed_size);
> }
> +#endif
>
> __decompress(input_data, input_len, NULL, NULL, output, output_len,
> NULL, error);
> --
It solved the problem.
next prev parent reply other threads:[~2023-09-08 6:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 11:48 Aaron Lu
2023-08-29 12:14 ` Bagas Sanjaya
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 [this message]
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=20230908060230.GA283801@ziqianlu-dell \
--to=aaron.lu@intel.com \
--cc=bagasdotme@gmail.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
all inboxes | Powered by JetHome®