mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Bainbridge <chris.bainbridge@canonical.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
	 Jason Miu <jasonmiu@google.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	 Alexander Graf <graf@amazon.com>,
	Ran Xiaokai <ran.xiaokai@zte.com.cn>,
	 regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
	kexec@lists.infradead.org,  linux-mm@kvack.org
Subject: Re: [BUG] KHO handover hangs when memmap reserves PMEM
Date: Tue, 6 Oct 2026 19:02:22 +0100	[thread overview]
Message-ID: <asU2AD6DxGSD0ek4@px13> (raw)
In-Reply-To: <asTTo3AFzQoqZLoP@kernel.org>

On Tue, Oct 06, 2026 at 12:55:31PM +0200, Mike Rapoport wrote:
> On Sat, Oct 03, 2026 at 06:02:27PM +0100, Chris Bainbridge wrote:
> > Hello,
> > 
> > I am reporting a regression in KHO handover.
> > 
> > In the most recent Ubuntu 26.10 beta mini-ISO releases (2026-09-18 onwards),
> > the first kernel reserves RAM for the downloaded ISO with a memmap directive
> > such as memmap=<size>!4G, then kexecs a second kernel. On affected kernels, the
> > first kernel reaches "kexec_core: Starting new kernel", but the second kernel
> > produces no further output and QEMU spins at 100% CPU. On unaffected kernels,
> > the second kernel starts and finds /dev/pmem0 with the expected "Persistent
> > Memory (legacy)" range in /proc/iomem.
> 
> TO make sure I understand this correctly, you enable KHO in the builds of
> the installer kernel and then the installer command line explicitly enables
> KHO.

Yes.

> Is there anything you actually preserve with KHO when kexec'ing the second
> kernel?

No. kho=off is a valid workaround for the mini ISO. I only reported it
as a regression here because this was working until the bisected commit
was merged. If this is intended behaviour then it is not a problem.

  reply	other threads:[~2026-10-06 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 17:02 Chris Bainbridge
2026-10-04 13:39 ` Pratyush Yadav
2026-10-04 15:09   ` Chris Bainbridge
2026-10-04 17:53     ` Pratyush Yadav
2026-10-06 10:55 ` Mike Rapoport
2026-10-06 18:02   ` Chris Bainbridge [this message]
2026-10-07  6:11     ` Mike Rapoport

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=asU2AD6DxGSD0ek4@px13 \
    --to=chris.bainbridge@canonical.com \
    --cc=graf@amazon.com \
    --cc=jasonmiu@google.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=ran.xiaokai@zte.com.cn \
    --cc=regressions@lists.linux.dev \
    --cc=rppt@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 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®