<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [ILK]igt/drv_suspend/sysfs-reader cause dmesg warn."
href="https://bugs.freedesktop.org/show_bug.cgi?id=88911#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [ILK]igt/drv_suspend/sysfs-reader cause dmesg warn."
href="https://bugs.freedesktop.org/show_bug.cgi?id=88911">bug 88911</a>
from <span class="vcard"><a class="email" href="mailto:hengx.ding@intel.com" title="Ding Heng <hengx.ding@intel.com>"> <span class="fn">Ding Heng</span></a>
</span></b>
<pre>f9b3927afbb97649f5c89f0815820167b7c5cba8 is the first bad commit.
commit f9b3927afbb97649f5c89f0815820167b7c5cba8
Author: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
AuthorDate: Wed Jan 28 14:43:24 2015 +0200
Commit: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
CommitDate: Fri Jan 30 17:15:31 2015 +0100
drm/i915: Do uncore early sanitize after domain init
intel_uncore_early_sanitize() will reset the forcewake registers. When
forcewake domains were introduced, the domain init was done after the
sanitization of the forcewake registers. And as the resetting of
registers use the domain accessors, we tried to reset the forcewake
registers with unitialized forcewake domains and failed.
Fix this by sanitizing after all the domains have been initialized. Do
per domain clearing of forcewake register on domain init so that
IVB can do early access to ECOBUS do determine the final configuration.
This regression was introduced in
commit 05a2fb157e44a53c79133805d30eaada43911941
Author: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
Date: Mon Jan 19 16:20:43 2015 +0200
drm/i915: Consolidate forcewake code
v2: Carve out ellc detect, fw_domain_reset for ivb/ecobus (Chris)
Bugzilla: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [VLV regression] MinnowBoard MAX DRM hang on linux-next 3.19-rc5 2015-01-26"
href="show_bug.cgi?id=88805">https://bugs.freedesktop.org/show_bug.cgi?id=88805</a>
Cc: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Reported-by: Olof Johansson <<a href="mailto:olof@lixom.net">olof@lixom.net</a>>
Tested-by: Darren Hart <<a href="mailto:dvhart@linux.intel.com">dvhart@linux.intel.com</a>> (v1)
Signed-off-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@intel.com">mika.kuoppala@intel.com</a>>
Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>