查看问题详情

编号项目分类查看权限最后更新
0000613Anolis OS 8crashpublic2022-01-27 14:21
报告员yinyongchen 分派给yunqi-zwt  
优先级normal严重性minor出现频率always
状态 assigned处理状况open 
平台aarch64操作系统Anolis OS操作系统版本8.4
标题0000613: [Anolis 8.4-5.10-aarch64] 升级 5.10.84-10_rc1 版本内核后,crash无法正常解析vmcore
描述[缺陷描述]:
 升级 5.10.84-10_rc1 版本内核后,crash无法正常解析vmcore

[重现概率]:
必现

[重现环境]:
环境信息:云上ECS
规格:

OS:
#cat /etc/os-release
NAME="Anolis OS"
VERSION="8.4"
ID="anolis"
ID_LIKE="rhel fedora centos"
VERSION_ID="8.4"
PLATFORM_ID="platform:an8"
PRETTY_NAME="Anolis OS 8.4"
ANSI_COLOR="0;31"
HOME_URL="https://openanolis.cn/"

KERNEL:
#uname -r
5.10.84-10_rc1.an8.aarch64

# rpm -qa | grep kernel
kernel-modules-4.19.91-23.4.an8.aarch64
kernel-modules-5.10.84-10_rc1.an8.aarch64
kernel-debuginfo-common-aarch64-5.10.84-10_rc1.an8.aarch64
kernel-modules-4.19.91-24.8.an8.aarch64
kernel-core-4.19.91-23.4.an8.aarch64
kernel-core-5.10.84-10_rc1.an8.aarch64
kernel-5.10.84-10_rc1.an8.aarch64
kernel-headers-5.10.84-10_rc1.an8.aarch64
kernel-debuginfo-5.10.84-10_rc1.an8.aarch64
kernel-devel-5.10.84-10_rc1.an8.aarch64
kernel-core-4.19.91-24.8.an8.aarch64
kernel-tools-libs-4.19.91-24.8.an8.aarch64
kernel-4.19.91-24.8.an8.aarch64
kernel-4.19.91-23.4.an8.aarch64
kernel-tools-4.19.91-24.8.an8.aarch64

MEMORY:
# free -h
              total used free shared buff/cache available
Mem: 122Gi 488Mi 121Gi 3.0Mi 1.0Gi 121Gi
Swap: 0B 0B 0B

CPU:
#lscpu
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 32
On-line CPU(s) list: 0-31
Thread(s) per core: 1
Core(s) per cluster: 32
Socket(s): 1
Cluster(s): 1
NUMA node(s): 1
Vendor ID: ARM
BIOS Vendor ID: Alibaba Cloud
Model: 1
Model name: Neoverse-N1
BIOS Model name: virt-rhel7.6.0
Stepping: r3p1
BogoMIPS: 50.00
NUMA node0 CPU(s): 0-31
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs

RPM:
# rpm -qa | grep -E "kexec-tools|crash"
kexec-tools-2.0.21-1.2.an8.aarch64
crash-7.2.9-2.an8.aarch64

CRASHKERNEL:
# cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/boot/vmlinuz-5.10.84-10_rc1.an8.aarch64 root=UUID=87264e5d-9651-489a-a856-55e6fb410d87 ro crashkernel=0M-2G:0M,2G-8G:192M,8G-:256M rhgb nvme_core.io_timeout=4294967295 quiet console=tty0 net.ifnames=0 console=ttyAMA0,115200n8

[期望结果]:
crash可以正常解析vmcore

[实际结果]:
crash无法解析vmcore,报错如下:
crash 7.2.9-2.an8
Copyright (C) 2002-2020 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.

WARNING: VA_BITS: calculated: 47 vmcoreinfo: 48
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu"...

WARNING: kernel relocated [0MB]: patching 106833 gdb minimal_symbol values

crash: invalid kernel virtual address: ffff001f57962050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57983050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f579a4050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f579c5050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f579e6050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57a07050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57a28050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57a49050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57a6a050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57a8b050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57aac050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57acd050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57aee050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57b0f050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57b30050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57b51050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57b72050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57b93050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57bb4050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57bd5050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57bf6050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57c17050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57c38050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57c59050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57c7a050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57c9b050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57cbc050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57cdd050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57cfe050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57d1f050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57d40050 type: "IRQ stack pointer"
crash: invalid kernel virtual address: ffff001f57d61050 type: "IRQ stack pointer"

crash: cannot resolve "__exception_text_start"
问题重现步骤1、手动触发crash ,执行echo c > /proc/sysrq-trigger
2、等待重启后使用crash命令查看生成的vmcore
标签没加标签.

活动

yinyongchen

2021-12-21 17:45

报告者  

image.png (116,560 字节)   
image.png (116,560 字节)   

yinyongchen

2022-01-05 11:00

报告者   ~0000875

升级到 5.10.84-10_rc2.an8.aarch64 版本内核后,crash依然无法解析vmcore,报错与rc1相同

anolis_account

2022-01-26 18:45

报告者   ~0000889

https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1
ubuntu 上crash-7.2.8-1ubuntu1声称解决了这个问题
image-2.png (5,264 字节)   
image-2.png (5,264 字节)   

Shiloong

2022-01-27 14:18

开发人员   ~0000890

最后编辑: 2022-01-27 14:21

@anolis_account:https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1
ubuntu 上crash-7.2.8-1ubuntu1声称解决了这个问题[附件]
-----------------------------------------------------------------------------------------------------------------------------------
这个补丁早在 crash-7.2.8已经合入, 解决的不是这个问题.
这个问题的 bugfix 如下, 在 crash-7.3.1合入:
https://github.com/crash-utility/crash/commit/f53b73e8380bca054cebd2b61ff118c46609429b

安装 crash-7.3.1-3.el8.aarch64.rpm 验证通过.

@yunqi-zwt 帮忙看看, 升级一下 crash

问题历史

日期 用户名 字段 更改
2021-12-21 17:45 yinyongchen 新建问题
2021-12-21 17:45 yinyongchen 添加了以下文件:: image.png
2022-01-05 11:00 yinyongchen 注释已添加: 0000875
2022-01-26 18:45 anolis_account 注释已添加: 0000889
2022-01-26 18:45 anolis_account 添加了以下文件:: image-2.png
2022-01-27 14:18 Shiloong 注释已添加: 0000890
2022-01-27 14:20 Shiloong 分派给 => yunqi-zwt
2022-01-27 14:20 Shiloong 状态 新建 => 已分配
2022-01-27 14:20 Shiloong 分类 kernel => crash
2022-01-27 14:20 Shiloong 描述已修改
2022-01-27 14:20 Shiloong 问题重现步骤已修改
2022-01-27 14:21 Shiloong 注释已编辑: 0000890
2022-01-27 14:21 Shiloong 注释已编辑: 0000890
2022-01-27 14:21 Shiloong 注释已编辑: 0000890