<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 4.4.0-rc7: [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue" href="https://bugs.freedesktop.org/show_bug.cgi?id=93710#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 4.4.0-rc7: [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue" href="https://bugs.freedesktop.org/show_bug.cgi?id=93710">bug 93710</a> from <a class="email" href="mailto:mmokrejs@fold.natur.cuni.cz" title="Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>"> Martin Mokrejs</a> <pre>(In reply to Martin Mokrejs from <a href="show_bug.cgi?id=93710#c4">comment #4</a>) > (In reply to Chris Wilson from <a href="show_bug.cgi?id=93710#c3">comment #3</a>) > > > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>