Created attachment 121845 [details] kern.log.bz2 Hardware: Motherboard: SawTooth Peak cpu model name : Intel(R) Core(TM) i7-4550U CPU @ 1.50GHz cpu model: 69 cpu family: 6 Graphic card: Haswell-ULT Integrated Graphics Controller (rev 09) Bios: HSWLPTU1.86C.0135.R01.1311020052 Linux distribution: Ubuntu 15.10 64 bits Kernel drm-intel-nightly 4.5.0-rc3_cdb3ed2 from http://cgit.freedesktop.org/drm-intel/ Libdrm: 2.4.66 Steps: ------ 1. Execute commands: cd <...>/intel-gpu-tools ./gem_sync --run-subtest basic-blt Actual result: -------------- 1. Test is fail Expected result --------------- 1. Test is Pass Regression: ------------ Last known good commit: 8fb2feecca499d11e104264071ac55e273e23af5 First known fail commit: 14d2522cec46a6d7593d156678570b511d232bcb
(In reply to cprigent from comment #0) > Steps: > ------ > 1. Execute commands: > cd <...>/intel-gpu-tools > ./gem_sync --run-subtest basic-blt > > Actual result: > -------------- > 1. Test is fail Is that the output from the test?...
The kern.log doesn't contain the test execution.
*** Bug 94289 has been marked as a duplicate of this bug. ***
*** Bug 88651 has been marked as a duplicate of this bug. ***
Tested 10 times with the same DUT and another one with fresh setup, test is Pass. Hardware Platform: NB2840 14 in Haswell Ultrabook CPU: Core i7 4500 U CPUID: 0x4561 (family: 6, model: 0x45, stepping: 1) Chipset PCH: LynxPoint Software Linux distribution: Ubuntu 15.10 LTS 64 bits kernel 4.5.0 e7a7673 from https://cgit.freedesktop.org/drm-intel/ commit e7a7673e9840fe8b50a5a2894c75565ec7858a00 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Sat Mar 19 11:10:45 2016 +0100 drm-intel-nightly: 2016y-03m-19d-10h-09m-53s UTC integration manifest libdrm 2.4.67-7 49041c3 from git://anongit.freedesktop.org/mesa/drm cairo 1.15.2 db8a7f1 from git://anongit.freedesktop.org/cairo intel-gpu-tools 1.14 c19b049 from http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git
So closed as not reproducible.
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.