Bug 78891

Can you please make sure that this is not a regression in igt, but really a kernel regression? I.e. please downgrade igt to an older version which was known to work and retest.

This is due to rendercopy failing straight from init. And gem_seqno_wrap
is leaning on that. So i expect gem_render_copy to fail also.

I noticed that if I force gpu to reset itself, then after successful reset
the rendercopy works as expected.

(In reply to comment #2)
> This is due to rendercopy failing straight from init. And gem_seqno_wrap
> is leaning on that. So i expect gem_render_copy to fail also.
> 
> I noticed that if I force gpu to reset itself, then after successful reset
> the rendercopy works as expected.

Please test gem_render_copy after this gem_seqno_wrap failing.

The gpu reset doesn't always fix the situation. It seems that PDPs get left
sometimes to zero after init/reset.

Created attachment 99460 [details]
dmesg

(In reply to comment #3)
> (In reply to comment #2)
> > This is due to rendercopy failing straight from init. And gem_seqno_wrap
> > is leaning on that. So i expect gem_render_copy to fail also.
> > 
> > I noticed that if I force gpu to reset itself, then after successful reset
> > the rendercopy works as expected.
> 
> Please test gem_render_copy after this gem_seqno_wrap failing.
> 
> The gpu reset doesn't always fix the situation. It seems that PDPs get left
> sometimes to zero after init/reset.

[root@x-bdw09 tests]# ./gem_seqno_wrap
IGT-Version: 1.6-g737d248 (x86_64) (Linux: 3.15.0-rc3_drm-intel-nightly_0791a3_20140520+ x86_64)
Test assertion failure function cmp_bo, file gem_seqno_wrap.c:115:
Last errno: 0, Success
Failed assertion: *vaddr++ == val
1: 0xfffffffc differs from assumed 0x0
seqno_before_test 0x1,  approximated seqno on test fail 0x1
[root@x-bdw09 tests]# ./gem_render_copy
IGT-Version: 1.6-g737d248 (x86_64) (Linux: 3.15.0-rc3_drm-intel-nightly_0791a3_20140520+ x86_64)
Test assertion failure function scratch_buf_check, file gem_render_copy.c:117:
Last errno: 0, Success
Failed assertion: val == color
Expected 0xffff00ff, found 0xfff0ff00 at (502,502)
[root@x-bdw09 tests]# cat /proc/cmdline

Please test:
http://patchwork.freedesktop.org/patch/26784/

Please ignore. The test stopped passing for me at some point.

Please test: IGT patch http://patchwork.freedesktop.org/patch/27088/

(In reply to comment #7)
> Please test: IGT patch http://patchwork.freedesktop.org/patch/27088/

Test on latest -nightly(455a8fc4304af51a913e33763b72dd2849c11d0c) use igt with this patch. the result was pass.

Output:
./gem_seqno_wrap
IGT-Version: 1.6-g3c70e6a (x86_64) (Linux: 3.15.0-rc7_drm-intel-nightly_455a8f_20140603+ x86_64)

Verified on latest -nightly(8148006fc6cc97fea2b792c91c0968a038612355)

Created attachment 103570 [details]
dmesg

Test still failed on latest -nightly(e967a525207bd40ab446e2f809907039f88e66f3)
[root@x-bdw01 tests]# ./gem_seqno_wrap
IGT-Version: 1.7-gfcbc502 (x86_64) (Linux: 3.16.0-rc6_drm-intel-nightly_e967a5_20140727+ x86_64)
Test assertion failure function cmp_bo, file gem_seqno_wrap.c:112:
Failed assertion: *vaddr++ == val
1: 0xfffffffe differs from assumed 0x0
seqno_before_test 0x1,  approximated seqno on test fail 0x1

Closing this old report in favour of the new bug 81831 so that we don't confuse the new issue with the old.

(In reply to comment #11)
> Closing this old report in favour of the new bug 81831 so that we don't
> confuse the new issue with the old.

Verified. Thanks.

Closing verified+fixed.