<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c14">Comment # 14</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 <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>On Sat, Nov 9, 2013 at 12:17 PM, <<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>> wrote: > --- <a href="show_bug.cgi?id=71267#c13">Comment #13</a> from Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> --- > (In reply to <a href="show_bug.cgi?id=71267#c12">comment #12</a>) >> 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. > > 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. The work item should check whether it's run already (or whether we killed the vdd synchronously), so double-scheduling shouldn't be harmful. If that isn't, we have a big bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>