<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:jinxianx.guo@intel.com" title="Guo Jinxian <jinxianx.guo@intel.com>"> <span class="fn">Guo Jinxian</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_ASSIGNED "
   title="ASSIGNED - [BSW Bisected]igt/kms_flip subcases cause "WARNING: CPU: 0 PID: 3785 at drivers/gpu/drm/i915/intel_display.c:3486 intel_crtc_wait_for_pending_flips+0xdd/0x197 [i915]()""
   href="https://bugs.freedesktop.org/show_bug.cgi?id=83759">bug 83759</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Status</td>
           <td>NEEDINFO
           </td>
           <td>ASSIGNED
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_ASSIGNED "
   title="ASSIGNED - [BSW Bisected]igt/kms_flip subcases cause "WARNING: CPU: 0 PID: 3785 at drivers/gpu/drm/i915/intel_display.c:3486 intel_crtc_wait_for_pending_flips+0xdd/0x197 [i915]()""
   href="https://bugs.freedesktop.org/show_bug.cgi?id=83759#c3">Comment # 3</a>
              on <a class="bz_bug_link 
          bz_status_ASSIGNED "
   title="ASSIGNED - [BSW Bisected]igt/kms_flip subcases cause "WARNING: CPU: 0 PID: 3785 at drivers/gpu/drm/i915/intel_display.c:3486 intel_crtc_wait_for_pending_flips+0xdd/0x197 [i915]()""
   href="https://bugs.freedesktop.org/show_bug.cgi?id=83759">bug 83759</a>
              from <span class="vcard"><a class="email" href="mailto:jinxianx.guo@intel.com" title="Guo Jinxian <jinxianx.guo@intel.com>"> <span class="fn">Guo Jinxian</span></a>
</span></b>
        <pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=83759#c2">comment #2</a>)
<span class="quote">> (In reply to Guo Jinxian from <a href="show_bug.cgi?id=83759#c1">comment #1</a>)
> > e17ac6db2ef99388b750b2141c11974dc5742913 is the first bad commit 
> > commit e17ac6db2ef99388b750b2141c11974dc5742913 
> > Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> 
> > AuthorDate: Thu Oct 9 19:37:15 2014 +0300 
> > Commit: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>> 
> > CommitDate: Thu Oct 16 14:58:44 2014 +0300 

> Come on, the bug was reported 2014-09-11 12:55:22 EEST, a full month before
> the supposed culprit was committed.</span >

The result on pristine fail commit(449b3795f2a48c51ad1714cd5eab0179e37c6a85)
was changed to skip now. And the dmesg warning still able to reproduce on
latest next-queued. 
I tried to bisected it between 449b3795f2a48c51ad1714cd5eab0179e37c6a85 and
latest next-queud, and found that e17ac6db2ef99388b750b2141c11974dc5742913 is
the first bad commit.</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>