Comment # 4
on bug 95517
from lumetili@gmail.com
OK my 3D accelerated VirtualBox VM just got stuck and journalctl -kf started spitting out VM faults once a second in a loop, at first there's a: May 26 01:39:24 carrier kernel: radeon 0000:02:00.0: GPU fault detected: 146 0x0042080c May 26 01:39:24 carrier kernel: radeon 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00014482 May 26 01:39:24 carrier kernel: radeon 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0200800C May 26 01:39:24 carrier kernel: VM fault (0x0c, vmid 1) at page 83074, read from TC (8) And then a: May 26 01:39:24 carrier kernel: radeon 0000:02:00.0: GPU fault detected: 146 0x0390350c May 26 01:39:24 carrier kernel: radeon 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0000C49C May 26 01:39:24 carrier kernel: radeon 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x1003500C May 26 01:39:24 carrier kernel: VM fault (0x0c, vmid 8) at page 50332, read from VGT (53) It devolves into looping the VGT entry with VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0000C4A<NUMBER> with NUMBER cycling from 0..F
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
