[Bug 101967] Hang on render ring (since updating to openSUSE 42.2 -> 42.3)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Jul 29 09:46:00 UTC 2017


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

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to kolAflash from comment #4)
> Created attachment 133120 [details]
> /sys/class/drm/card0/error from 2017-07-29T08:20:17
> 
> Looks like drm-kmp-default-4.9.33_k4.4.76_1-5.1.x86_64.rpm fixed only half
> of the bug.
> 
> Now the the system just hangs for a moment (about 10 sec.), but then it
> continues running normally. And the SC2_x64.exe isn't totally crashed any
> more.
> 
> 2017-07-29T08:20:17.993239+02:00 gaston kernel: [    0.000000] Kernel
> command line: BOOT_IMAGE=/vmlinuz-4.4.76-1-default
> root=/dev/mapper/system-root resume=/dev/system/swap splash=silent quiet
> showopts drm.vblankoffdelay=1 i915.enable_rc6=7 i915.lvds_downclock=1
> [...]
> 2017-07-29T09:24:34.803016+02:00 gaston kernel: [ 3891.933914] [drm] GPU
> HANG: ecode 6:0:0x85fffffc, in SC2_x64.exe [7167], reason: Hang on render
> ring, action: reset
> [...]
> 2017-07-29T09:24:34.803057+02:00 gaston kernel: [ 3891.933917] [drm] GPU
> crash dump saved to /sys/class/drm/card0/error
> 2017-07-29T09:24:34.803059+02:00 gaston kernel: [ 3891.933951] drm/i915:
> Resetting chip after gpu hang
> 
> Interestingly the last line ("drm/i915: Resetting chip after gpu hang")
> comes only once. Before installing
> drm-kmp-default-4.9.33_k4.4.76_1-5.1.x86_64.rpm that line repeated without
> end about every 10 seconds.
> 
> A guess:
> The drm-kmp-default-4.9.33_k4.4.76_1-5.1.x86_64.rpm didn't fixed the bug
> itself but it makes the gpu recover correctly when resetting.

You've confused two different issues. The first GPU hang was the loss of
context state on mempressure or suspend. Your second GPU hang is from StarCraft
running on mesa. Update mesa and if that doesn't resolve the issue file a bug
against mesa:drivers/i965.

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


More information about the intel-gfx-bugs mailing list