<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW] live_hangcheck - Failed to start request"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100457#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW] live_hangcheck - Failed to start request"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100457">bug 100457</a>
from <span class="vcard"><a class="email" href="mailto:matthew.auld@intel.com" title="mwa <matthew.auld@intel.com>"> <span class="fn">mwa</span></a>
</span></b>
<pre>Okay, so bisection pointed to:
commit e09a3036412a959689bacf017bf2cbc226c9fea4
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Tue Apr 11 11:13:39 2017 +0100
drm/i915: Use __intel_uncore_wait_for_register_fw for sandybride_pcode_read
Since the sandybridge_pcode_read() may be called from
skl_pcode_request() inside an atomic context (with preempt disabled), we
should avoid hitting any sleeping paths. Currently is being called with
a 500ms timeout, irrespective of being inside an atomic context or not.
This is reduced down to 500us to play nice with the atomic context, and
that appears to be sufficient to keep BAT happy (we have a DRM_ERROR
should it timeout), i.e. we do not see any 500us pcode timeouts for
normal use. So leave it as a pure spin without having to introduce new
code paths to separate atomic/normal contexts.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>