On Tue, Nov 18, 2014 at 04:00:58PM -0800, shuang...@intel.com wrote: > Tested-By: PRC QA PRTS (Patch Regression Test System Contact: > shuang...@intel.com) > -------------------------------------Summary------------------------------------- > Platform: baseline_drm_intel_nightly_pass_rate->patch_applied_pass_rate > BYT: pass/total=290/290->290/290 > PNV: pass/total=362/362->362/362 > ILK: pass/total=381/381->381/381 > IVB: pass/total=522/559->522/559 > SNB: pass/total=444/444->444/444 > HSW: pass/total=595/595->595/595 > BDW: pass/total=436/436->435/436 > -------------------------------------Detailed------------------------------------- > test_platform: test_suite, test_case, result_with_drm_intel_nightly(count, > machine_id...)...->result_with_patch_applied(count, machine_id)... > BDW: Intel_gpu_tools, igt_gem_reset_stats_close-pending-ctx-render, PASS(4, > M28) -> FAIL(1, M28)PASS(3, M28)
This patch /should/ fix a pretty decent amount of WARN backtrace in modeset tests on hsw/bdw (as long as there's a hdmi screen around). Instead it causes a completely unrelated test to fail. Can you please dig into what's going on here? -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
