<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BYT Regression]igt/kms_pipe_crc_basic causes system hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=81704#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BYT Regression]igt/kms_pipe_crc_basic causes system hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=81704">bug 81704</a> from <a class="email" href="mailto:jinxianx.guo@intel.com" title="Guo Jinxian <jinxianx.guo@intel.com>"> Guo Jinxian</a> <pre>f8bf63fdcb1f82459dae7a3f22ee5ce92f3ea727 is the first bad commit commit f8bf63fdcb1f82459dae7a3f22ee5ce92f3ea727 Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> AuthorDate: Fri Jun 13 13:37:54 2014 +0300 Commit: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> CommitDate: Mon Jul 7 11:27:52 2014 +0200 drm/i915: Kill duplicated cdclk readout code from i2c We have a slightly different way of readoing out the cdclk in gmbus_set_freq(). Kill that and just call .get_display_clock_speed(). Also need to remove the GMBUSFREQ update from intel_i2c_reset() since that gets called way too early. Let's do it in intel_modeset_init_hw() instead, and also pull the initial vlv_cdclk_freq update there from init_clock gating. Signed-off-by: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> Reviewed-by: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>> Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> :040000 040000 8929124f54d2ca2c16d6f179e288e22ba360b895 3e32e9591f25ba2264d38d3de38ed5230e9b1e30 M drivers The parents commit 7d007f40596670c8fddfae583952b091b02cf0eb doesn't causes system hang. But revert the bad commit base on latest commit (f68d697eaf3278200a7fc3c8b1d95d72837b84d8), the test still causes system hang</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>