Created attachment 120576 [details] Contents of /sys/class/drm/card0/error I noticed the game becoming unresponsive for a few seconds while playing; I saw this in my kernel messages later: [240918.898139] [drm] stuck on render ring [240918.898845] [drm] GPU HANG: ecode 7:0:0x85dffff8, in lotroclient.exe [13281], reason: Ring hung, action: reset [240918.898846] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [240918.898846] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [240918.898847] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [240918.898847] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [240918.898847] [drm] GPU crash dump saved to /sys/class/drm/card0/error [240918.900045] drm/i915: Resetting chip after gpu hang This is on an i5 4690k (HD graphics 4600) running with intel_iommu=on. I'm not sure how reproducible this is.
Created attachment 120577 [details] System information
From dump, we can note that we have in render ring : FAULT_REG: 0x000000c7 Valid Invalid and Unloaded PD Fault (PPGTT) Address 0x00000000 Source ID 24 and also in this log: ERROR: 0x00000105 TLB page fault error (GTT entry not valid) Invalid page directory entry error Cacheline containing a PD was marked as invalid There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.
(In reply to yann from comment #2) > From dump, we can note that we have in render ring : > FAULT_REG: 0x000000c7 > Valid > Invalid and Unloaded PD Fault (PPGTT) > Address 0x00000000 > Source ID 24 > > and also in this log: > ERROR: 0x00000105 > TLB page fault error (GTT entry not valid) > Invalid page directory entry error > Cacheline containing a PD was marked as invalid > > There were improvements pushed in kernel and Mesa that will benefit to your > system, so please re-test with latest kernel & Mesa to see if this issue is > still occurring. Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa (12-13) to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.