[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a0d9847-54df-47f3-9e96-be393f76b3fb@linux.vnet.ibm.com>
Date: Fri, 14 Feb 2025 12:10:21 +0530
From: Venkat Rao Bagalkote <venkat88@...ux.vnet.ibm.com>
To: Hari Bathini <hbathini@...ux.ibm.com>, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org
Cc: Sourabh Jain <sourabhjain@...ux.ibm.com>
Subject: Re: [linux-next-20250212] syscall kexec_file_load not available
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@...-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@...-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@...-zzci-1 ~]# kexec -v
>> kexec-tools 2.0.27
>> [root@...-zzci-1 ~]# uname -r
>> 6.14.0-rc2-next-20250212
>>
>
> Is the kernel built with CONFIG_KEXEC_FILE ?
>
> - Hari
>
Powered by blists - more mailing lists