/ 详情

5.10 内核 crash 无法复位

Done
Task
Opened this issue  
2021-05-11 21:07

启动参数如下:
linux /vmlinuz-5.10.0.base+ root=/dev/mapper/euleros-root ro crash_kexec_post_notifiers softlockup_panic=1 panic=1 reserve_kbox_mem=16M vga=0x317 nohz=off fsck.mode=auto fsck.repair=yes crashkernel=512M rd.lvm.lv=euleros/root rd.lvm.lv=euleros/swap rd.shell=0 smmu.bypassdev=0x1000:0x17 smmu.bypassdev=0x1000:0x15 video=VGA-1:640x480-32@60me

kdump启动:
[root@localhost ~]# service kdump status
Redirecting to /bin/systemctl status kdump.service
● kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2021-05-11 11:00:36 CST; 9h ago
Process: 780 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)
Main PID: 780 (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CGroup: /system.slice/kdump.service

内核crash时,机子卡死,无法复位。

例如:
echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger

手动注入panic,4.19内核能复位。但是5.10内核卡死不能复位。

输入图片说明

Attachments

Comments (2)

Hey lixiaokeng, Welcome to openEuler Community.
All of the projects in openEuler Community are maintained by @openeuler-ci-bot .
That means the developers can comment below every pull request or issue to trigger Bot Commands.
Please follow instructions at https://gitee.com/openeuler/community/blob/master/en/sig-infrastructure/command.md to find the details.

lixiaokeng created任务
lixiaokeng set related repository to openEuler/kernel
lixiaokeng changed description
展开全部操作日志

该问题出现环境:EulerOS-V2R10替换成5.10版本的kernel。

重新使用openEuler-21.03的镜像环境:内核panic后可以生成vmcore。

表明该问题大概率是EulerOS环境下kdump和5.10内核不匹配。建议关闭issue

lixiaokeng changed issue state from 待办的 to 已完成

Sign in to comment

状态
Assignees
Projects
Milestones
Pull Requests
关联的 Pull Requests 被合并后可能会关闭此 issue
Branches
Planed to start   -   Planed to end
-
Top level
Priority
Duration (hours)
确定
参与者(3)
5329419 openeuler ci bot 1578984659