[Bug 93710] 4.4.0-rc7: [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=93710

--- Comment #4 from Martin Mokrejs <mmokrejs at fold.natur.cuni.cz> ---
(In reply to Chris Wilson from comment #3)

> Hmm, the vsync region is right up to the last scanline (give or take the
> granularity). Do you see the error if you move the window off the bottom of
> the screen?

I do not understand. I have just one screen, via HDMI to an external display.
The internal LVDS display of the laptop is disabled. I can only add that when I
leave my computer and turn off the external LCD, then after returning back and
turning on the external LCD power it has no signal and the laptop's LCD is
enabled. I have to use arandr to swap the outputs. I don't remember having to
use arandr for a while. Maybe some code is too eager to disable the HDMI
output? I would dare to guess that this (need to use arandr to re-enable HDMI
output) is a consequence of the GPU HANG, because I realized this only after
the GPU HANG.

> 
> Also the error state is reporting GPU page faults from the context and VT'd.
> A recent drm-intel-nightly kernel should fix the context fault, and can you
> try intel_iommu=off?

I can after I reboot after some days.

> 
> Do you see the same error on older kernels?

You can search bugzilla for my previous reports with GPU HANGs, I have no idea
which have the same traces. But with 4.3.0, 4.3.3, 3.18.xx I did not see it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160115/c30ad38f/attachment.html>