[Bug 78268] [HSW Bisected]Many subtests of igt/kms_flip fail

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=78268

Guo Jinxian <jinxianx.guo at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED

--- Comment #7 from Guo Jinxian <jinxianx.guo at intel.com> ---
(In reply to comment #6)
> (In reply to comment #5)
> > bisected on the bad hsw device.
> > 33e8465e8759077106474cbf4f3d87612c41411d is the first bad commit
> > 
> > commit 33e8465e8759077106474cbf4f3d87612c41411d
> > Author:     Imre Deak <imre.deak at intel.com>
> > AuthorDate: Fri Apr 25 13:19:05 2014 +0300
> > Commit:     Daniel Vetter <daniel.vetter at ffwll.ch>
> > CommitDate: Wed Apr 30 10:06:25 2014 +0200
> > 
> >     drm/i915: vlv: init only needed state during early power well enabling
> > 
> >     During the initial power well enabling on the driver init/resume path
> >     we can avoid initialzing part of the HW/SW state that will be
> >     initialized anyway by the subsequent init/resume code. For some steps
> >     like HPD initialization this redundancy is not only an overhead but an
> >     actual problem, since they can't be run this early in the overall init
> >     sequence.
> > 
> >     Add a flag marking the init phase and skip reinitialzing state that is
> >     not strictly necessary based on that.
> > 
> >     This is also needed by the upcoming HPD init restructuring by Thierry
> >     and Daniel.
> > 
> >     Signed-off-by: Imre Deak <imre.deak at intel.com>
> >     Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>
> > 
> > Revert this commit, the test result was passed.
> 
> This commit doesn't affect HSW, as it changes only VLV specific parts. Maybe
> the problem you're seeing doesn't happen always resulting in an incorrect
> bisect result. Could you try testing each commit multiple times to make sure
> you don't hit the problem already before the above commit in the bisect
> sequence?

Yes, the problem you're seeing doesn't happen always. I tried 20 times for each
commit, and find the first bad commit below.

5bb0c2fd8c41dbee8ada1124d625c05765cd3f02 is the first bad commit
commit 5bb0c2fd8c41dbee8ada1124d625c05765cd3f02
Author:     Ben Widawsky <benjamin.widawsky at intel.com>
AuthorDate: Fri Apr 18 18:04:29 2014 -0300
Commit:     Daniel Vetter <daniel.vetter at ffwll.ch>
CommitDate: Wed Apr 30 10:06:19 2014 +0200

    drm/i915/bdw: Disable idle DOP clock gating

    It seems we need this at least for the current platforms we have, but
    probably not later. In any event, it should cause too much harm as we do
    the same thing on several other platforms.

    Signed-off-by: Ben Widawsky <ben at bwidawsk.net>
    Signed-off-by: Rodrigo Vivi <rodrigo.vivi at gmail.com>
    Reviewed-by: Brad Volkin <bradley.d.volkin at intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>


But I revert this commit and run the test again, this issue still able to
reproduce.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140527/54d45306/attachment-0001.html>