System Environment: -------------------------- Platform: SNB/IVB/HSW/BYT kernel: (drm-intel-fixes)09f2344d0896eb458a639b922224c7a202c11599 Bug detailed description: --------------------------- Many gem_reset_stats subcases fail on sandybridge, ivybridge, haswell and baytrail with -queued, -fixes and -nightly kernel. They are new cases. run ./gem_reset_stats --run-subtest ban-render output: IGT-Version: 1.5-g5b91475 (x86_64) (Linux: 3.13.0-rc7_drm-intel-fixes_09f234_20140120+ x86_64) reset status for 7 ctx 0 returned -22 Test assertion failure function test_ban, file gem_reset_stats.c:521: Last errno: 22, Invalid argument Failed assertion: _assert_reset_status(fd_bad, 0, 0) == 0 Subtest ban-render: FAIL Following subcases fail: igt/gem_reset_stats/ban-blt igt/gem_reset_stats/ban-bsd igt/gem_reset_stats/ban-ctx-render igt/gem_reset_stats/ban-render igt/gem_reset_stats/ban-vebox igt/gem_reset_stats/close-pending-blt igt/gem_reset_stats/close-pending-bsd igt/gem_reset_stats/close-pending-ctx-render igt/gem_reset_stats/close-pending-fork-blt igt/gem_reset_stats/close-pending-fork-bsd igt/gem_reset_stats/close-pending-fork-render igt/gem_reset_stats/close-pending-fork-vebox igt/gem_reset_stats/close-pending-render igt/gem_reset_stats/close-pending-vebox igt/gem_reset_stats/reset-count-blt igt/gem_reset_stats/reset-count-bsd igt/gem_reset_stats/reset-count-ctx-render igt/gem_reset_stats/reset-count-render igt/gem_reset_stats/reset-count-vebox igt/gem_reset_stats/reset-stats-blt igt/gem_reset_stats/reset-stats-bsd igt/gem_reset_stats/reset-stats-ctx-render igt/gem_reset_stats/reset-stats-render igt/gem_reset_stats/reset-stats-vebox igt/gem_reset_stats/unrelated-ctx-render
Created attachment 92499 [details] dmesg
The functionality of getting reset stats (ioctl) is not yet in drm-intel-fixes. The ioctl is present in drm-intel-next-queued and drm-intel-nightly. Please reopen this one if SKIP return is preferred for kernels that don't have the ioctl. I would rather keep this as failing case.
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.