[Bug 89629] [i965 regression]igt/kms_rotation_crc/sprite-rotation causes WARNING: CPU: 0 PID: 4126 at drivers/gpu/drm/drm_irq.c:1133 drm_wait_one_vblank+0x3b/0x16d [drm]()
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Nov 30 00:37:10 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=89629
--- Comment #4 from Carlos Santa <carlos.santa at intel.com> ---
(In reply to Carlos Santa from comment #3)
> @jani, christophe
>
> this bug can't be reproduced because the test no longer exists as it was
> reported (bug report is from more than a year ago).
>
> The commit that changed the test is this one:
>
> commit e1ce5eac338f44deda488a44db04faceea12f13a
> Author: Sonika Jindal <sonika.jindal at intel.com>
> Date: Wed Apr 22 16:44:05 2015 +0530
>
> kms_rotation_crc: Adding test for 90/270 rotation
>
> Adding 90/270 rotation testcase for primary and sprite planes.
>
> v2: Added position test for sprite. Checking for gen > 9 for 90/270.
> Some cleanup and rebase.
> v3: Added test for unsupported tiling and unsupported pixel format for
> 90/270
> v4: Added the legacy commit to initiate modeset in the negative
> test(Tvrtko)
>
> Signed-off-by: Sonika Jindal <sonika.jindal at intel.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
> Signed-off-by: Thomas Wood <thomas.wood at intel.com>
>
> However, running the newer tests (sprite-rotation-180, sprite-rotation-270,
> sprite-rotation-90, sprite-rotation-90-pos-100-0) they all get reported as
> failures but for a different reason.
>
> We need to close this bug as not invalid and then open new bugs for each of
> the new test cases that are now failing.
>
> How should we proceed?
>
> Carlos
Sorry, above, I meant to say this should be close as invalid...
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161130/429c25aa/attachment.html>
More information about the intel-gfx-bugs
mailing list