<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71267#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71267">bug 71267</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=71267#c12">comment #12</a>)
<span class="quote">> I wonder a bit though who's hogging the kms lock - we chase an awful lot of
> pointers to get at it, so if someone's corrupting this I expect we'd blow
> up. And lockdep shouldn't be too happy about it either. Confusing.</span >
My theory is that the work item is being called twice. Crazy, huh? But since we
seem to be very cavalier in scheduling the work even if it is already queued, I
think it is reasonable to assume that we shoot ourselves in the foot.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>