<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SNB CI] multi-minute cpu stall when running kms_flip@blt-wf_vblank-vs-dpms|modeset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102262">102262</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[SNB CI] multi-minute cpu stall when running kms_flip@blt-wf_vblank-vs-dpms|modeset
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>daniel@ffwll.ch
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>This bug just for recording for posterity what we found out:
On snb CI shards (gt1, but I managed to kill my gt2 a few times too) the system
can seemingly hard-hang when running the above testcases. This was tested on
igt commits
commit c8811338e8a7723b5e99a303361ed97c092fc270 (HEAD -> master, fdo/master)
Author: Kelvin Gardiner <<a href="mailto:kelvin.gardiner@intel.com">kelvin.gardiner@intel.com</a>>
Date: Tue Jun 27 14:04:51 2017 -0700
intel-ci: Add fast-feedback-simulation.testlist
Kernel integration manifest is roughly
drm-intel drm-intel-fixes 781cc76e0c2469cb7ac12ba238a4ea006978e321
drm/i915: Avoid the gpu reset vs. modeset deadlock
drm-upstream drm-fixes 46828dc77961d9286e55671c4dd3b6c9effadf1a
Merge branch 'linux-4.13' of git://github.com/skeggsb/linux into
drm-fixes
drm-intel drm-intel-next-fixes 04941829b0049d2446c7042ab9686dd057d809a6
drm/i915: Hold RPM wakelock while initializing OA buffer
drm-intel drm-intel-next-queued 4e34935fcf691b2f553fdc34502d649bf979a06f
drm/i915/cnl: Setup PAT Index.
drm-upstream drm-next 0c697fafc66830ca7d5dc19123a1d0641deaa1f6
Backmerge tag 'v4.13-rc5' into drm-next
sound-upstream for-next c9480d055e306a855f8a8d2b3b097773cd0d5ad0
sound: emu8000: constify emu8000_ops
sound-upstream for-linus a8e800fe0f68bc28ce309914f47e432742b865ed
ALSA: usb-audio: Apply sample rate quirk to Sennheiser headset
drm-intel topic/core-for-CI 01cbe29aa8f8d7ffca23cf6e147a17529fae680e
e1000e: fix buffer overrun while the I219 is processing DMA
transactions
drm-misc drm-misc-next b9c55b6e2cc4369b0688961fa5de0e057f3ec0c4
drm/vc4: Continue the switch to drm_*_put() helpers
drm-misc drm-misc-next-fixes 1ed134e6526b1b513a14fba938f6d96aa1c7f3dd
drm/vc4: Fix VBLANK handling in crtc->enable() path
drm-misc drm-misc-fixes a0ffc51e20e90e0c1c2491de2b4b03f48b6caaba
drm/atomic: If the atomic check fails, return its value first
I'll attach a netconsole log of a typical death, but tldr is that we stall for
a few minutes (with not even the NMI watchdog being able to do anything) until
eventually the system recovers and the batch completes and the dpms/modeset-off
goes through.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>