<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [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]()" href="https://bugs.freedesktop.org/show_bug.cgi?id=89629#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [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]()" href="https://bugs.freedesktop.org/show_bug.cgi?id=89629">bug 89629</a> from <a class="email" href="mailto:carlos.santa@intel.com" title="Carlos Santa <carlos.santa@intel.com>"> Carlos Santa</a> <pre>@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 <<a href="mailto:sonika.jindal@intel.com">sonika.jindal@intel.com</a>> 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 <<a href="mailto:sonika.jindal@intel.com">sonika.jindal@intel.com</a>> Reviewed-by: Tvrtko Ursulin <<a href="mailto:tvrtko.ursulin@intel.com">tvrtko.ursulin@intel.com</a>> Signed-off-by: Thomas Wood <<a href="mailto:thomas.wood@intel.com">thomas.wood@intel.com</a>> 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</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>