396 Star 1.4K Fork 1.3K

GVPopenEuler / kernel

 / 详情

loongarch kvm启动时发生panic

已完成
缺陷
创建于  
2024-01-23 20:18

【标题描述】能够简要描述问题:说明什么场景下,做了什么操作,出现什么问题(尽量使用正向表达方式)
loongarch kvm启动时发生panic
一、缺陷信息

内核信息:
5.10.0.176
缺陷归属组件:
kvm
缺陷归属的版本:

缺陷简述:
loongarch架构下启动qemu kvm物理机panic

【环境信息】
硬件信息

  • 裸机场景请提供问题的硬件信息
  • 虚拟机场景请提供虚拟机的XML文件或配置信息
    软件信息
  • OS版本及分支信息
  • 内核信息
  • 发现问题的组件版本信息
    网络信息
  • 如果有特殊组网,请提供网络拓扑信息

【问题复现步骤】,请描述具体的操作步骤
loongarch架构下通过virt-manager启动qemu kvm
【实际结果】,请描述出问题的结果和影响
物理机内核panic
[ 35.513694][ T1594] CPU: 0 PID: 1594 Comm: qemu-kvm Not tainted 5.10.0+ #1
[ 35.520523][ T1594] Hardware name: Loongson Loongson-3A5000-HV-7A2000-1w-V0.1-EVB/Loongson-LS3A5000-7A2000-1w-EVB-V1.21, BIOS Loongson-UDK2018-V4.0.05380-beta10 1
[ 35.534956][ T1594] $ 0 : 0000000000000000 900000000040c6b8 900000010f61c000 900000010f61fc60
[ 35.543606][ T1594] $ 4 : 900000011e3ac758 0000000000000000 900000010f611f00 ffff800002764c28
[ 35.552254][ T1594] $ 8 : 900000010f61fc08 ffffff0001583048 0000000000000080 00000000000d0046
[ 35.560901][ T1594] $12 : ffffffffffffffff 0000000000000001 0000000000000001 0000000000000003
[ 35.569550][ T1594] $16 : 000000000000000f 9000000130603000 00000000000006e6 0000000000000000
[ 35.578198][ T1594] $20 : 9000000158308000 000000aaaef80000 90000000014008c0 900000011e3ad758
[ 35.586845][ T1594] $24 : 900000010f61fcc0 0000000000000001 0000000000000000 9000000000f72000
[ 35.595494][ T1594] $28 : 900000010f610000 0000000000000001 000000aaaef80000 9000000130603000
[ 35.604161][ T1594] era : ffff800002754d88 kvm_mmu_notifier_invalidate_range_end+0x90/0x94 [kvm]
[ 35.613073][ T1594] ra : 900000000040c6b8 __mmu_notifier_invalidate_range_end+0x90/0x128
[ 35.621371][ T1594] CSR crmd: aaaef80000
[ 35.621372][ T1594] CSR prmd: 00000004
[ 35.625350][ T1594] CSR euen: 900000010f610000
[ 35.629154][ T1594] CSR ecfg: 9000000130603000
[ 35.633650][ T1594] CSR estat: 900000011f9e9960
[ 35.642729][ T1594] ExcCode : 1e (SubCode 7e)
[ 35.647053][ T1594] PrId : 0014c011 (Loongson-64bit)
[ 35.652067][ T1594] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nft_objref nf_conntrack_tftp tun bridge stp llc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_t
[ 35.726630][ T1594] Process qemu-kvm (pid: 1594, threadinfo=0000000091e50370, task=00000000094710cb)
[ 35.735705][ T1594] Stack : 900000011e3ad758 900000000040c6b8 0000000000000008 900000011f9e9960
[ 35.744354][ T1594] ffffff0001575f00 ffffff0001575f00 900000010f61fd50 90000000003bcf34
[ 35.753001][ T1594] 900000010f61fcc0 fffffffffffffffd ffffffffffffff97 0000000000000001
[ 35.761649][ T1594] 900000011f9e9960 9000000130603000 000000aaaef80000 000000aaaef84000
[ 35.770296][ T1594] 0000000100000001 0000000000000000 900000011e4e9000 000000fffbde1fb0
[ 35.778944][ T1594] 0000000000000001 9000000130603068 0000000000000040 9000000130603000
[ 35.787591][ T1594] 900000010f680050 0000000000000255 900000011f9e9960 900000010f61fd50
[ 35.796239][ T1594] 0000000000000004 90000000003c4b18 900000011f9e9960 00100cca00000255
[ 35.804887][ T1594] 00000000000002e9 000000aaaef80000 900000010f616ab8 900000010f680050
[ 35.813534][ T1594] 40000001575f029d 0000000000000000 ffffff0001575f00 900000010f611f00
[ 35.822182][ T1594] ...
[ 35.825296][ T1594] Call Trace:
[ 35.825302][ T1594] [] kvm_mmu_notifier_invalidate_range_end+0x90/0x94 [kvm]
[ 35.836974][ T1594] [<900000000040c6b8>] __mmu_notifier_invalidate_range_end+0x90/0x128
[ 35.844929][ T1594] [<90000000003bcf34>] wp_page_copy+0x654/0xba4
[ 35.850981][ T1594] [<90000000003c4b18>] __handle_mm_fault+0xfc/0x3a0
[ 35.857380][ T1594] [<90000000003c4eac>] handle_mm_fault+0xf0/0x258
[ 35.863605][ T1594] [<900000000023071c>] __do_page_fault+0x110/0x370
[ 35.869916][ T1594] [<90000000002309cc>] do_page_fault+0x50/0x7c
[ 35.875882][ T1594] [<900000000022fcd8>] tlb_do_page_fault_1+0xf4/0x190
[ 35.882453][ T1594]
[ 35.884616][ T1594] Code: 4c000020 55779000 53ffbbff <002a0001> 02ff0063 29c0c077 29c0e061 29c0a078 29c08079
[ 35.894999][ T1594]
[ 35.897211][ T1594] ---[ end trace 71c7030e5032cbeb ]---
[ 35.902494][ T1594] Kernel panic - not syncing: Fatal exception
[ 35.908383][ T1594] ---[ end Kernel panic - not syncing: Fatal exception ]---

【其他相关附件信息】
比如系统message日志/组件日志、dump信息、图片等

缺陷详情参考链接:

缺陷分析指导链接:
https:xxx
怀疑下面patch的合入导致loongarch物理机panic
commit ID ac63cf0a8e38a3569ab927f34e700d3a0d178336
KVM: Move MMU notifier's mmu_lock acquisition into common helper
loongarch架构使用旧的mmu notifier机制
在kvm_mmu_notifier_invalidate_range_end函数中会对 kvm->mmu_notifier_count--;
但是在kvm_mmu_notifier_invalidate_range_start函数中却没有kvm->mmu_notifier_count++;

评论 (1)

lixianglai 创建了缺陷

Hi lixianglai, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

openeuler-ci-bot 添加了
 
sig/Kernel
标签
lixianglai 修改了描述
lixianglai 修改了描述
zhangjialin 添加了
 
help-wanted
标签
Yu Zhang 通过openeuler/kernel Pull Request !4261任务状态待办的 修改为已完成

登录 后才可以发表评论

状态
负责人
项目
里程碑
Pull Requests
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
开始日期   -   截止日期
-
置顶选项
优先级
预计工期 (小时)
参与者(2)
5329419 openeuler ci bot 1632792936
C
1
https://gitee.com/openeuler/kernel.git
git@gitee.com:openeuler/kernel.git
openeuler
kernel
kernel

搜索帮助