Created attachment 118579 [details] Dmesg logs Test enviroment: Name: drm-intel-testing Description: IGT tools manage all basic functions for graphics stack CPU: Intel(R) CPU @ 1.60GHz Board: : Wilson Beach DVT2 Ultrabook GPU: SoC: Broadwell 2+2 D0 (QDF : QGHA) Kernel 4.3.0-rc8-drm-intel-testing-2015-08-28 Mesa: mesa-10.6.7 from http://cgit.freedesktop.org/mesa/mesa/ Xf86_video_intel: 2.99.917 from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ Libdrm: libdrm-2.4.64 from http://cgit.freedesktop.org/mesa/drm/ Cairo: 1.14.2 from http://cgit.freedesktop.org/cairo libva: libva-1.6.0 from http://cgit.freedesktop.org/libva/ intel-driver: 1.6.1. from http://cgit.freedesktop.org/vaapi/intel-driver xorg: 1.17.99 installed with script git_xorg.sh Xserver: xorg-server-1.17.2 from http://cgit.freedesktop.org/xorg/xserver Intel-gpu-tools: 1.12 from http://cgit.freedesktop.org/xorg/app/intel-gpu Steps to reproduce: 1. Install intel graphic stack with mentioned configuration 2. Install igt 3. Execute ./run-test.sh -t gme_ppgtt@flink-and-close-vma-leak Expected result: Test should exit without issues Actual Result: Returncode 99 Time 0:00:00.051469 Stdout IGT-Version: 1.12-g1f9e055 (x86_64) (Linux: 4.3.0-rc2-drm-intel-nightly+ x86_64) Stack trace: #0 [__igt_fail_assert+0xf1] #1 [_start+0x0] #2 [__libc_start_main+0xf5] #3 [_start+0x29] #4 [<unknown>+0x29] Subtest flink-and-close-vma-leak: FAIL (0.016s) Stderr Test assertion failure function flink_and_close, file gem_ppgtt.c:261: Failed assertion: offset == offset_new error: 262144 != 266240 Subtest flink-and-close-vma-leak failed. **** DEBUG **** Test requirement passed: fd >= 0 Test requirement passed: uses_full_ppgtt(fd) Test requirement passed: fd >= 0 Test assertion failure function flink_and_close, file gem_ppgtt.c:261: Failed assertion: offset == offset_new error: 262144 != 266240 **** END ****
*** This bug has been marked as a duplicate of bug 90400 ***
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.