Created attachment 103578 [details] dmesg ==System Environment== -------------------------- Regression: Yes. Good commit on -next-queued: 9c33baa6b3bbb01c1a88dceba986b20e6642cf31 Non-working platforms: BDW ==kernel== -------------------------- origin/drm-intel-nightly: e967a525207bd40ab446e2f809907039f88e66f3(fails) drm-intel-nightly: 2014y-07m-25d-23h-02m-06s integration manifest origin/drm-intel-next-queued: eff9b57c1a91ccf309d57500ab6a365ba7be5712(fails) drm/i915: Update DRIVER_DATE to 20140725 origin/drm-intel-fixes: f4be89cecea437aaddd7700d05c6bdb5678041f7(works) drm/i915: Fix crash when failing to parse MIPI VBT ==Bug detailed description== igt/gem_seqno_wrap fails Output: root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_seqno_wrap IGT-Version: 1.7-gfcbc502 (x86_64) (Linux: 3.16.0-rc6_drm-intel-nightly_e967a5_20140728+ x86_64) Test assertion failure function cmp_bo, file gem_seqno_wrap.c:112: Failed assertion: *vaddr++ == val 1: 0xfffffff9 differs from assumed 0x0 seqno_before_test 0x1, approximated seqno on test fail 0x1 ==Reproduce steps== ---------------------------- 1. ./gem_seqno_wrap
Smells like a dup of https://bugs.freedesktop.org/show_bug.cgi?id=81209
But semaphores are disabled in this test, right? I guess we need an automated state dumper for when tests fail.
(In reply to comment #2) > But semaphores are disabled in this test, right? I guess we need an > automated state dumper for when tests fail. Test passed on latest -nightly(45cb75c77746cc3023acdfb4033e745d1d6024d9) root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_seqno_wrap IGT-Version: 1.7-gf473a55 (x86_64) (Linux: 3.17.0-rc2_drm-intel-nightly_45cb75_20140902+ x86_64) root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# echo $? 0 root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# cat /sys/kernel/debug/dri/0/i915_semaphore_status Semaphores are disabled
*** 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.