From: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>
Subject: Re: [linux-next-20250212] syscall kexec_file_load not available
Date: Fri, 14 Feb 2025 12:10:21 +0530 [thread overview]
Message-ID: <5a0d9847-54df-47f3-9e96-be393f76b3fb@linux.vnet.ibm.com> (raw)
In-Reply-To: <77c11ea2-f3ae-497a-aaba-f7b33f46743d@linux.ibm.com>
Yes Hari, its built with CONFIG_KEXEC_FILE=y
Regards,
Venkat.
On 14/02/25 12:02 pm, Hari Bathini wrote:
>
>
> On 13/02/25 8:34 pm, Venkat Rao Bagalkote wrote:
>> Greetings!!!
>>
>> From kernel next-20250210, I am observing syscall kexec_file_load
>> not available, there by kdump service is failing to start.
>>
>>
>> Logs:
>>
>> [root@ltc-zzci-1 ~]# kexec -p --initrd=/boot/initramfs-6.14.0-rc2-
>> next-20250212kdump.img /boot/vmlinuz-6.14.0-rc2-next-20250212 -c
>> Warning: append= option is not passed. Using the first kernel root
>> partition
>> Modified cmdline: elfcorehdr=311424K root=UUID=b5b1f89c-
>> d479-48b3-90e2-744a2fd05667
>> [root@ltc-zzci-1 ~]# kexec -p --initrd=/boot/initramfs-6.14.0-rc2-
>> next-20250212kdump.img /boot/vmlinuz-6.14.0-rc2-next-20250212 -s
>> syscall kexec_file_load not available.
>> [root@ltc-zzci-1 ~]# kexec -v
>> kexec-tools 2.0.27
>> [root@ltc-zzci-1 ~]# uname -r
>> 6.14.0-rc2-next-20250212
>>
>
> Is the kernel built with CONFIG_KEXEC_FILE ?
>
> - Hari
>
next prev parent reply other threads:[~2025-02-14 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 15:04 [linux-next-20250212] syscall kexec_file_load not available Venkat Rao Bagalkote
2025-02-14 3:44 ` Sourabh Jain
2025-02-14 6:32 ` Hari Bathini
2025-02-14 6:40 ` Venkat Rao Bagalkote [this message]
2025-02-14 6:45 ` Sourabh Jain
2025-02-14 7:08 ` Hari Bathini
2025-02-14 7:21 ` Sourabh Jain
2025-02-14 14:43 ` Sourabh Jain
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=5a0d9847-54df-47f3-9e96-be393f76b3fb@linux.vnet.ibm.com \
--to=venkat88@linux.vnet.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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