Created attachment 92258 [details] dmesg System Environment: -------------------------- Platform: Broadwell Kernel: (drm-intel-nightly)4acca65d00ccbabbe6481f2521a17a134050a427 Bug detailed description: ------------------------- It fails on Broad well with -nightly kernel. It's a new case. output: IGT-Version: 1.5-g1552aa2 (x86_64) (Linux: 3.13.0-rc7_drm-intel-nightly_4acca6_20140117+ x86_64) Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Reproduce steps: ---------------------------- 1. ./gem_gtt_hog
This is a new one from Chris.
Not so fast - the error is that coherency on bdw is bust.
Oh, now I remember, it is just missing the bdw blit fixes. Whoever feels like a trivial job...
Hi lu hua, Could you please test with this intel-gpu-tools bdw-blts branch: http://cgit.freedesktop.org/~vivijim/intel-gpu-tools/log/?h=bdw-blts
The last version on my branch was buggy, so if you tested it, please update the branch and test it again. Current version should fix this issue.
It still fails on latest igt and -nightly kernel. output: IGT-Version: 1.5-g971c7db (x86_64) (Linux: 3.13.0_drm-intel-nightly_8f5284_20140208+ x86_64) Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Test assertion failure function run, file gem_gtt_hog.c:143: Last errno: 2, No such file or directory Failed assertion: x == canary Also test the patch, It still fails.
I'm sorry. I had forgotten to update my repository. Please git fetch && git rebase to_my_remote/bdw-blts and test again.
Created attachment 95905 [details] output Test on latest igt and -nightly kernel(b18596), It still fails.
(In reply to comment #9) > Hi lu hua, > > Could you please test with this intel-gpu-tools bdw-blts branch: > http://cgit.freedesktop.org/~vivijim/intel-gpu-tools/log/?h=bdw-blts It works well on bdw-blts branch. output IGT-Version: 1.6-g8abf2b9 (x86_64) (Linux: 3.14.0-rc6_drm-intel-nightly_b18596_20140314+ x86_64) Time to execute 64 children: 326834.255ms
Patches has been merged. So closing this entry. Feel free to reopen if you still face this issue on i-g-t master. thanks, Rodrigo.
Verified.Fixed.
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.