Bug 850 - [Anolis OS 8.4 龙芯版][4.19.190-4.an8.loongarch64]kdump.service loaded failed, /boot下缺失kdump kernel和initrd导致
Summary: [Anolis OS 8.4 龙芯版][4.19.190-4.an8.loongarch64]kdump.service loaded failed, /...
Status: RESOLVED DUPLICATE of bug 3726
Alias: None
Product: Anolis OS 8
Classification: Anolis OS
Component: BaseOS Packages (show other bugs) BaseOS Packages
Version: 8.4
Hardware: loongarch Linux
: P2-High S2-major
Target Milestone: ---
Assignee: HFD
QA Contact: shuming
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-15 10:33 UTC by bolong_tbl
Modified: 2023-01-17 15:07 UTC (History)
1 user (show)

See Also:


Attachments
kdump.service loaded failed (546.37 KB, image/png)
2022-04-15 10:33 UTC, bolong_tbl
Details
/etc/sysconfig/kdump (297.43 KB, image/png)
2022-04-15 10:37 UTC, bolong_tbl
Details
ls /boot (150.23 KB, image/png)
2022-04-15 11:06 UTC, bolong_tbl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bolong_tbl alibaba_cloud_group 2022-04-15 10:33:48 UTC
Created attachment 185 [details]
kdump.service loaded failed

Description of problem:
/boot下缺失kdump kernel和initrd文件,导致kdump.service loaded failed

Version-Release number of selected component (if applicable):
内核版本:4.19.190-4.an8.loongarch64
kexec-tools版本:2.0.22-2.an8.loongarch64


Steps to Reproduce:
1.物理机上图形化安装Anolis 8.4龙芯版镜像
2.yum install kexec-tools
3.修改crashkernel=128M后reboot机器
4.systemctl start kdump
5.systemctl status kdump

Actual results:
kdump.service loaded failed

Expected results:
kdump.service 运行正常

Additional info:
Comment 1 bolong_tbl alibaba_cloud_group 2022-04-15 10:37:56 UTC
Created attachment 186 [details]
/etc/sysconfig/kdump

/etc/sysconfig/kdump 配置默认寻找/boot/vmlinux-$(uname -r)+kdump.img和/boot/initramfs-$(uname -r)+kdump.img
Comment 2 bolong_tbl alibaba_cloud_group 2022-04-15 11:06:36 UTC
Created attachment 187 [details]
ls /boot

/boot下没有所需的kdump kernel和initrd,如附件所示
Comment 3 葛立伟 alibaba_cloud_group 2023-01-17 15:07:23 UTC
暂时不支持通用方案

*** This bug has been marked as a duplicate of bug 3726 ***