linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Mike Rapoport <rppt@kernel.org>
Cc: Donet Tom <donettom@linux.ibm.com>,
	Hari Bathini <hbathini@linux.ibm.com>,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	linux-mm@kvack.org
Subject: Re: powerpc/fadump: CMA init is failing
Date: Fri, 27 Feb 2026 22:39:53 +0530	[thread overview]
Message-ID: <87o6lagljy.ritesh.list@gmail.com> (raw)
In-Reply-To: <4c338a29-d190-44f3-8874-6cfa0a031f0b@linux.ibm.com>

Sourabh Jain <sourabhjain@linux.ibm.com> writes:

> I noticed CMA init for fadump crashkernel memory is failing.
>
> [    0.000000] cma: pageblock_order not yet initialized. Called during 
> early boot?
> [    0.000000] fadump: Failed to init cma area for firmware-assisted 
> dump,-22
>
>
> kernel command-line:
> BOOT_IMAGE=(ieee1275//vdevice/v-scsi@30000070/disk@8100000000000000,msdos2)/vmlinuz-7.0.0-rc1+ 
> root=/dev/mapper/rhel_ltcden3--lp12-root ro 
> rd.lvm.lv=rhel_ltcden3-lp12/root rd.lvm.lv=rhel_ltcden3-lp12/swap 
> fadump=on crashkernel=3G
>
>
> Same issue with kdump CMA reservation:
>
> [    0.000000][    T0] cma: pageblock_order not yet initialized. Called 
> during early boot?

Good that we added those debug prints ;)

I think I know what went wrong, as part of this arch,mm consolidation
patch series [1], I think the order of initialization is changed.

With this patch the new order is ... 
start_kernel()
    - setup_arch()
       - xxx_cma_reserve();
    - mm_core_init_early()
       - free_area_init()
          - sparse_init()
             - set_pageblock_order() // this sets the pageblock_order.

Whereas earlier set_pageblock_order() was called from initmem_init(),
just before cma reservations were being made. 

start_kernel()
    - setup_arch()
       - initmem_init()
         - sparse_init()
           - set_pageblock_order();  // this sets the pageblock_order
       - xxx_cma_reserve();

So that means, pageblock_order is not initialized before these cma
reservation function calls, hence we are seeing these failures.

setup_arch() {
    ...

	/*
	 * Reserve large chunks of memory for use by CMA for kdump, fadump, KVM and
	 * hugetlb. These must be called after initmem_init(), so that
	 * pageblock_order is initialised.
	 */
	fadump_cma_init();
	kdump_cma_reserve();
	kvm_cma_reserve();

    ...
}


So what if we do.. 

start_kernel() {
  ...
	setup_arch(&command_line);
	mm_core_init_early();
    setup_arch_post_mm_core_init(); // and here we call CMA reservation functions ?


References:
[1]: https://lore.kernel.org/linuxppc-dev/20260111082105.290734-1-rppt@kernel.org/T/#m5adf1a845e0a0867066c4f7055f28e6304b73fa5
[2]: https://lore.kernel.org/all/3ae208e48c0d9cefe53d2dc4f593388067405b7d.1729146153.git.ritesh.list@gmail.com/


-ritesh


       reply	other threads:[~2026-02-27 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4c338a29-d190-44f3-8874-6cfa0a031f0b@linux.ibm.com>
2026-02-27 17:09 ` Ritesh Harjani [this message]
2026-02-27 20:50   ` 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=87o6lagljy.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=donettom@linux.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=rppt@kernel.org \
    --cc=sourabhjain@linux.ibm.com \
    /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