From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Donet Tom <donettom@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>
Subject: powerpc/fadump: CMA init is failing
Date: Fri, 27 Feb 2026 20:49:28 +0530 [thread overview]
Message-ID: <4c338a29-d190-44f3-8874-6cfa0a031f0b@linux.ibm.com> (raw)
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?
[ 0.000000][ T0] cma: Failed to reserve 200 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 100 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 50 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 25 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 12 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 6 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 3 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 1 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 0 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 0 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 0 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 0 MiB
[ 0.000000][ T0] cma: pageblock_order not yet initialized. Called
during early boot?
[ 0.000000][ T0] cma: Failed to reserve 0 MiB
[ 0.000000][ T0] crashkernel CMA reservation failed: 200 MB
requested, 0 MB reserved in 0 ranges
kernel command-line:
# cat /proc/cmdline
noreboot crashkernel=200M crashkernel=200M,cma
Should be easy to reproduce it with powerpc defconfig:
make ARCH=powerpc defconfig
The crashkernel CMA init for fadump and kdump happens in:
arch/powerpc/kernel/setup-common.c -> setup_arch()
initmem_init();
/*
* 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();
Has something changed for pageblock_order initialization?
- Sourabh Jain
next reply other threads:[~2026-02-27 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:19 Sourabh Jain [this message]
2026-02-27 17:09 ` powerpc/fadump: CMA init is failing Ritesh Harjani
2026-02-27 20:50 ` Mike Rapoport
2026-02-28 2:35 ` Ritesh Harjani
2026-02-28 13:46 ` Sourabh Jain
2026-02-28 17:54 ` Ritesh Harjani
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=4c338a29-d190-44f3-8874-6cfa0a031f0b@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=donettom@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=ritesh.list@gmail.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