Created attachment 116447 [details] dmesg ==System Environment== -------------------------- Regression: yes/igt regression good commit: 0d16473df4ed29c9836b03090c78debfb9a7e3e6 bad commit: fd772e32a23157fc29649070a6a5e94d70ae02f8 Non-working platforms:all ==kernel== -------------------------- drm-intel-nightly/a2ed0c64452ef98160ea849f2e742ce6c077e645 commit a2ed0c64452ef98160ea849f2e742ce6c077e645 Author: Jani Nikula <jani.nikula@intel.com> Date: Tue Jun 9 10:42:12 2015 +0300 drm-intel-nightly: 2015y-06m-09d-07h-41m-49s UTC integration manifest ==Bug detailed description== ----------------------------- It fails on all platforms. following cases also fail: igt@gem_streaming_writes@cpu-sync igt@gem_streaming_writes@gtt igt@gem_streaming_writes@gtt-sync igt@gem_streaming_writes@wc igt@gem_streaming_writes@wc-sync output: IGT-Version: 1.10-gfd772e3 (x86_64) (Linux: 4.1.0-rc7_drm-intel-nightly_a2ed0c_20150610+ x86_64) Test assertion failure function test_streaming, file gem_streaming_writes.c:216: Failed assertion: __dst_offset == dst_offset Stack trace: #0 [__igt_fail_assert+0xf1] #1 [test_streaming+0x657] #2 [__real_main370+0x38e] #3 [main+0x29] #4 [__libc_start_main+0xf5] #5 [_start+0x29] #6 [<unknown>+0x29] Subtest cpu failed. **** DEBUG **** Test requirement passed: ret == 0 Test requirement passed: __gem_execbuf(fd, &execbuf) == 0 Test assertion failure function test_streaming, file gem_streaming_writes.c:216: Failed assertion: __dst_offset == dst_offset **** END **** Subtest cpu: FAIL (0.004s) ==Reproduce steps== ---------------------------- 1. ./gem_streaming_writes --run-subtest cpu
Bug scrub: Assigned to Olivier. We will check if reproduced with last kernel and igt 1.11.
commit 0591af9c76f21b1d9afd067adc6946799fc29179 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Jul 28 20:02:54 2015 +0100 igt/gem_streaming_writes: Reorder setting EXEC_OBJECT_WRITE Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90944 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
I've tested the following tests on both kernels, drm-intel-nitghly and testing This the results for both kernels : Kernel : latest drm-intel-testing (4.3.0-rc6-testing) commit 87074657f22e38163e712ca417e1a398d00096b6 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Fri Oct 23 11:56:52 2015 +0200 test = gem_streaming_writes --run-subtest cpu BDW-ULT = pass SNB = pass HSW-U = pass BYT-M =pass SKL-U = pass test = gem_streaming_writes --run-subtest cpu-sync BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass test = gem_streaming_writes --run-subtest gtt BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass test = gem_streaming_writes --run-subtest gtt-sync BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass test = gem_streaming_writes --run-subtest wc BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass test = gem_streaming_writes --run-subtest wc-sync BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass Kernel : latest drm-intel-nightly: 2015y-11m-06d-12h-48m-02s UTC integration manifest commit a3b0dec82fdb59c629c4fb9847245b80b0cf69dd Author: Jani Nikula <jani.nikula@intel.com> Date: Fri Nov 6 14:48:23 2015 +0200 test = gem_streaming_writes --run-subtest cpu BDW-ULT = pass SNB = pass HSW-U = pass BYT-M =pass SKL-U = pass test = gem_streaming_writes --run-subtest cpu-sync BDW-ULT = pass SNB = pass HSW-U = pass BYT-M =pass SKL-U = pass test = gem_streaming_writes --run-subtest gtt BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass test = gem_streaming_writes --run-subtest gtt-sync BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass test = gem_streaming_writes --run-subtest wc BDW-ULT = pass SNB = pass HSW-U = pass BYT-M =pass SKL-U = pass test = gem_streaming_writes --run-subtest wc-sync BDW-ULT = pass SNB = pass HSW-U = pass BYT-M = pass SKL-U = pass This is a verification with all the platforms and the bug isnt present
Thanks for the verification. So closed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.