Created attachment 102735 [details] dmesg ==System Environment== -------------------------- Regression: Yes Good commit on -next-queued: 91565c85b66db820f01894a971d39aaef60c4325 Non-working platforms: BDW ==kernel== -------------------------- origin/drm-intel-nightly: 271bff129a641b5b35d99c9eb0ceb866ca42f692(fails) drm-intel-nightly: 2014y-07m-12d-12h-07m-51s integration manifest origin/drm-intel-next-queued: 491a3448622059b087d8c465b46b11f2953df7c1(fails) drm/i915: Enable PSR by default. origin/drm-intel-fixes: ceb9f032dc858c349d7d213454c5ba2c6ef9c5e5(works) Revert "drm/i915: Don't set the 8to6 dither flag when not scaling" ==Bug detailed description== igt/gem_reset_stats/close-pending-bsd causes " [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning!" Output: root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_reset_stats --run-subtest close-pending-bsd IGT-Version: 1.7-ge74dd22 (x86_64) (Linux: 3.16.0-rc4_drm-intel-nightly_271bff_20140713+ x86_64) Subtest close-pending-bsd: SUCCESS root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg -r | egrep ""<[1-3]>"" |grep drm <3>[ 897.218423] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning! <3>[ 909.224583] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning! ==Reproduce steps== ---------------------------- 1. ./gem_reset_stats --run-subtest close-pending-bsd
So i915.semaphores=0 prevents the hang?
(In reply to comment #1) > So i915.semaphores=0 prevents the hang? Yes, boot the device with "i915.semaphores=0", test result was passed. root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_reset_stats --run-subtest close-pending-bsd IGT-Version: 1.7-g4d4f4b2 (x86_64) (Linux: 3.16.0-rc5_drm-intel-nightly_873440_20140721_debug+ x86_64) Subtest close-pending-bsd: SUCCESS
*** This bug has been marked as a duplicate of bug 81209 ***
Closing resolved+duplicate as duplicate of closed+fixed.
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.