Bug 95361

Summary: [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle
Product: DRI Reporter: mikhail.v.gavrilov
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: gary.c.wang, intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: HSW i915 features: GPU hang
Attachments:
Description Flags
dmesg
none
GPU crash dump none

Description mikhail.v.gavrilov 2016-05-12 03:23:54 UTC 
Created attachment 123636 [details]
dmesg

GPU hangs when I try play video file

$ uname -r
4.5.3-300.fc24.x86_64

$ rpm -qa | grep intel
xorg-x11-drv-intel-2.99.917-22.20160119.fc24.x86_64
Comment 1 mikhail.v.gavrilov 2016-05-12 03:24:21 UTC 
Created attachment 123637 [details]
GPU crash dump
Comment 2 yann 2016-06-03 07:35:40 UTC 
*** Bug 96353 has been marked as a duplicate of this bug. ***
Comment 3 Chris Wilson 2016-08-10 10:16:47 UTC 
commit 83348ba84ee0d5d4d982e5382bfbc8b2a2d05e75
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Aug 9 17:47:51 2016 +0100

    drm/i915: Move missed interrupt detection from hangcheck to breadcrumbs
    
    In commit 2529d57050af ("drm/i915: Drop racy markup of missed-irqs from
    idle-worker") the racy detection of missed interrupts was removed when
    we went idle. This however opened up the issue that the stuck waiters
    were not being reported, causing a test case failure. If we move the
    stuck waiter detection out of hangcheck and into the breadcrumb
    mechanims (i.e. the waiter) itself, we can avoid this issue entirely.
    This leaves hangcheck looking for a stuck GPU (inspecting for request
    advancement and HEAD motion), and breadcrumbs looking for a stuck
    waiter - hopefully make both easier to understand by their segregation.

*** This bug has been marked as a duplicate of bug 96902 ***

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.