From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [linux-next-20250212] syscall kexec_file_load not available
Date: Fri, 14 Feb 2025 09:14:19 +0530 [thread overview]
Message-ID: <bdc8c274-960e-4f66-9790-736e9bd0eb76@linux.ibm.com> (raw)
In-Reply-To: <8e73069b-5987-4a08-b13d-13fe691092ad@linux.vnet.ibm.com>
Hello Venkat,
On 13/02/25 20:34, 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.
>
powerpc do have support for kexec_file_load system. Seems like there is
an issue.
Thanks for reporting the issue.
I will debug and find what went wrong with next-20250210 or the kexec
you used to load the kdump kernel.
Thanks,
Sourabh Jain
>
> 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
>
>
> Regards,
>
> Venkat.
>
next prev parent reply other threads:[~2025-02-14 3:44 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 [this message]
2025-02-14 6:32 ` Hari Bathini
2025-02-14 6:40 ` Venkat Rao Bagalkote
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=bdc8c274-960e-4f66-9790-736e9bd0eb76@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=venkat88@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.