Created attachment 107807 [details] dmesg ==System Environment== -------------------------- Regression: Yes. It's a igt regression bug Good commit: b498d81f152760b2a58d53ac3acb5269f44a253d Bud commit: a0b5c6d2ee784a8ea49534050087b3c630a41bc4 Non-working platforms: BYT ==kernel== -------------------------- origin/drm-intel-nightly: 2ea23cd593ba60ead60e2f796fae675aa4475b1a(fails) drm-intel-nightly: 2014y-10m-13d-09h-34m-29s UTC integration manifest origin/drm-intel-next-queued: fff95501f2095fa8a9dbd7e177bbf642d241b2fe(fails) drm/i915: intel_backlight scale() math WA origin/drm-intel-fixes: bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9(fails) Linux 3.17 ==Bug detailed description== igt/gem_bad_reloc/negative-reloc skips Output: root@x-byt06:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_bad_reloc --run-subtest negative-reloc IGT-Version: 1.8-gca6b63f (x86_64) (Linux: 3.17.0_drm-intel-nightly_2ea23c_20141014_debug+ x86_64) Found offset 8736768 for 4k batch Test requirement not met in function negative_reloc, file gem_bad_reloc.c:90: Test requirement: gem_exec[0].offset < BIAS Subtest negative-reloc: SKIP (0.002s) ==Reproduce steps== ---------------------------- 1. ./gem_bad_reloc --run-subtest negative-reloc
This is perplexing as the SKIP only depends upon GTT state inside the kernel and should not have been affected by igt (except for perhaps a leaky test). So bisect if you can.
The result passes on latest -nightly(2ea23cd593ba60ead60e2f796fae675aa4475b1a) root@x-byt06:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_bad_reloc --run-subtest negative-reloc IGT-Version: 1.8-g5c7d54e (x86_64) (Linux: 3.17.0_drm-intel-nightly_2ea23c_20141016+ x86_64) Found offset 0 for 4k batch Batch is now at offset 262144 Subtest negative-reloc: SUCCESS (0.001s)
Closing old verified.
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.