Comment # 8
on bug 85207
from Andy Furniss
(In reply to Andy Furniss from comment #7) > (In reply to Christian König from comment #6) > > (In reply to Andy Furniss from comment #5) > > > I don't know about Elemental as it's far harder to trigger, but first try > > > with valley produced - > > > > > > [ 156.617954] radeon 0000:01:00.0: GPU fault detected: 146 0x02e83504 > > > [ 156.617960] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR > > > 0x00010F17 > > > [ 156.617961] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS > > > 0x08035004 > > > [ 156.617963] VM fault (0x04, vmid 4) at page 69399, read from VGT (53) > > > > Sounds like a different problem triggered by the same patchset to me. > > > > But first things first, is the original issue with the list corruption > > fixed? If yes we can start to look into this one as well. > > It's OK so far, but then I need more time as I don't really know how to > trigger it and last time I called it as OK (in another bug) it wasn't. Still haven't crashed Elemental but have got - [29066.333908] [drm:radeon_gem_va_update_vm] *ERROR* Couldn't update BO_VA (-512) [29066.335653] [drm:radeon_gem_va_update_vm] *ERROR* Couldn't update BO_VA (-512)
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
