[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 bugzilla-daemon at freedesktop.org
Wed Jan 20 01:56:52 PST 2016


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

--- Comment #5 from Martin Mokrejs <mmokrejs at fold.natur.cuni.cz> ---
(In reply to Martin Mokrejs from comment #4)
> (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.

The need to use arandr/xrandr to re-enable external HDMI and to disable
internal LVDS is not related to the GPU hang. After a few other bootups with
the same kernel and runtime options I conclude this is some new issue with the
kernel elsewhere. It happens whenever I power off my external LCD (not if it
just falls asleep and get woken up).


> > 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.

I booted up several times but so far I never hit the GPU HANG. Therefore, I
don't think even trying intel_iommu=off would help us getting any conclusion.
It just does not manifest often enough.

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


More information about the intel-gfx-bugs mailing list