Request device [07:08.2] fault addr 0x0 fault reason [0x02] Present bit in context entry is clear

EmilZackrisson

New Member
Mar 24, 2023
3
1
3
Sweden
Hi!
My Proxmox server have been crashing randomly and today it happend again so I started to try solve it.
I tried to only run unRaid and I noticed that it runs fine until I start a parity check. Then Proxmox almost imedietly freezes and prints what looks like a PCIe error on the screen (see picture) https://imgur.com/a/SkxYTlN. I have attached the output from lspci and lshw.

Best regards.
 

Attachments

Do you use PCI passthrough?
If not, have you tried disabling IOMMU yet?

What's the output of pveversion -v and the VM config? qm config <VMID>
 
Do you use PCI passthrough?
If not, have you tried disabling IOMMU yet?

What's the output of pveversion -v and the VM config? qm config <VMID>
Yes, i'm using PCI passthrough. I have not tried disablning IOMMU because then I can't test if it's working correctly.

After I first posted I updated the kernel and decreased the RAM to the VM. As of now, it seems to be working fine. But it only crashes sometimes with irregular intervals. Sometimes it's been up for 3 months and other times under 3 hours. Any idea why?

pveversion -v
proxmox-ve: 8.0.2 (running kernel: 6.2.16-15-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
proxmox-kernel-helper: 8.0.3
pve-kernel-5.15: 7.4-5
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2: 6.2.16-15
proxmox-kernel-6.2.16-10-pve: 6.2.16-10
pve-kernel-5.15.111-1-pve: 5.15.111-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.26-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.5
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.9
libpve-guest-common-perl: 5.0.5
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.3-1
proxmox-backup-file-restore: 3.0.3-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.9
pve-cluster: 8.0.4
pve-container: 5.0.4
pve-docs: 8.0.5
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.8-2
pve-ha-manager: 4.0.2
pve-i18n: 3.0.7
pve-qemu-kvm: 8.0.2-6
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.7
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.13-pve1

qm config 100
agent: 1
balloon: 0
bios: ovmf
boot: order=usb0
cores: 4
cpu: host
hostpci0: 0000:07:00,pcie=1
hostpci1: 0000:02:00,pcie=1
machine: q35
memory: 12288
meta: creation-qemu=6.2.0,ctime=1675528832
name: unraid
net0: virtio=16:72:6F:22:63:95,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=1aea87f6-580c-4eed-9629-56f494f03051
sockets: 1
startup: order=1
usb0: host=0951:1666
usb1: host=0665:5161
vmgenid: db9e9a34-b9da-4308-b67a-115ff3a286a6
 
Sorry for the late reply.

Since this is quite the old platform, are you running the latest BIOS version?

Does it work if you boot the latest 5.15 kernel you have available instead of 6.2?
 
Sorry for the late reply.

Since this is quite the old platform, are you running the latest BIOS version?

Does it work if you boot the latest 5.15 kernel you have available instead of 6.2?
The BIOS is up to date.
It seems to be working at the moment since I updated the kernel and decreased RAM to the VM.
 
  • Like
Reactions: mira