Bug 105711

Summary: [CI] igt@gem_exec_await@wide-contexts - incomplete - Softdog - missing breadcrumb/i915_reset_device spam in dmesg
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: SNB i915 features: GEM/Other

Description Marta Löfstedt 2018-03-23 12:42:55 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4379/shard-snb7/igt@gem_exec_await@wide-contexts.html

run.log:
running: igt/gem_exec_await/wide-contexts  

[68/98] skip: 38, pass: 29, dmesg-warn: 1 |
owatch: TIMEOUT!
owatch: timeout for /dev/watchdog0 set to 10 (requested 10)

From dmesg:
<7>[  160.049683] [IGT] gem_exec_await: executing
<6>[  160.059436] [drm] GPU HANG: ecode 6:0:0xfffffffe, reason: Manually set wedged engine mask = ffffffffffffffff, action: reset
<7>[  160.059809] [drm:i915_reset_device [i915]] resetting chip
<5>[  160.060091] i915 0000:00:02.0: Resetting chip for Manually set wedged engine mask = ffffffffffffffff
<7>[  160.061573] [drm:init_workarounds_ring [i915]] rcs0: Number of context specific w/a: 0
<7>[  160.062723] [drm:vgem_gem_dumb_create [vgem]] Created object of size 1
<7>[  163.744049] missed_breadcrumb rcs0 missed breadcrumb at intel_breadcrumbs_hangcheck+0x5a/0x80 [i915]

then basically everything in dmesg is resets interleaved with missed_breadcrumb until owatch triggers softdog:
<7>[  173.728133] [drm:i915_reset_device [i915]] resetting chip
...
<7>[  187.744166] [drm:i915_reset_device [i915]] resetting chip
...
<7>[  311.712161] [drm:i915_reset_device [i915]] resetting chip
...
<7>[  507.744145] [drm:i915_reset_device [i915]] resetting chip
Comment 1 Marta Löfstedt 2018-04-18 06:43:44 UTC
This looks like a one off I lower priority to normal

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.