Kernel crash iommu

MinerAle00

Member
Apr 3, 2022
8
2
8
www.youtube.com
Hi guys, sometimes during the day my promxox server crash. This time i found the error on syslog but i dont know what is the problem. This is what i have seen on syslog.

------------[ cut here ]------------
Jul 25 18:50:52 ripper kernel: WARNING: CPU: 0 PID: 197 at drivers/iommu/dma-iommu.c:511 __iommu_dma_unmap+0x129/0x140
Jul 25 18:50:54 ripper kernel: Modules linked in: realtek nvme nvme_core iwlmvm mac80211 libarc4 iwlwifi igb dca cfg80211 i2c_algo_bit xhci_pci(+) xhci_pci_renesas xhci_hcd wmi mac_hid zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi vfio_pci vfio_pci_core vfio_virqfd irqbypass vfio_iommu_type1 vfio ip_tables x_tables autofs4 simplefb ahci libahci gpio_amdpt gpio_generic
Jul 25 18:50:54 ripper kernel: CPU: 0 PID: 197 Comm: kworker/u2:5 Tainted: P W O 5.15.39-1-pve #1
Jul 25 18:50:54 ripper kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X399 Taichi, BIOS P3.90 12/04/2019
Jul 25 18:50:54 ripper kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
Jul 25 18:50:54 ripper kernel: RIP: 0010:__iommu_dma_unmap+0x129/0x140
Jul 25 18:50:54 ripper kernel: Code: 48 c7 45 b0 00 00 00 00 48 c7 45 b8 00 00 00 00 48 c7 45 c0 00 00 00 00 48 c7 45 c8 00 00 00 00 48 c7 45 a8 ff ff ff ff eb 8d <0f> 0b e9 74 ff ff ff e8 2b 36 50 00 66 66 2e 0f 1f 84 00 00 00 00
Jul 25 18:50:54 ripper kernel: RSP: 0018:ffffadddc0937c38 EFLAGS: 00010206
Jul 25 18:50:54 unknow:

uname -r
5.15.39-1-pve

Package versions
proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-6 pve-kernel-helper: 7.2-6 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.39-1-pve: 5.15.39-1 pve-kernel-5.15.35-3-pve: 5.15.35-6 pve-kernel-5.13.19-6-pve: 5.13.19-15 pve-kernel-5.13.19-2-pve: 5.13.19-4 ceph: 16.2.9-pve1 ceph-fuse: 16.2.9-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve1 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-4 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-2 libpve-guest-common-perl: 4.1-2 libpve-http-server-perl: 4.1-3 libpve-storage-perl: 7.2-7 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.0-3 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.2.5-1 proxmox-backup-file-restore: 2.2.5-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.1 pve-cluster: 7.2-2 pve-container: 4.2-2 pve-docs: 7.2-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.5-1 pve-ha-manager: 3.4.0 pve-i18n: 2.7-2 pve-qemu-kvm: 6.2.0-11 pve-xtermjs: 4.16.0-1 qemu-server: 7.2-3 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.4-pve1
 
mhmm thats only a warning.. can you post more of the log?
what is your hardware? what kind of vms do you run ? any correlation between the crash and some action (e.g. vm start/stop)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!