[Bug 110940] igt at kms_* - skip - No second valid output found / Can't test dual pipes with the current outputs

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=110940

--- Comment #6 from Martin Peres <martin.peres at free.fr> ---
(In reply to Jani Saarinen from comment #4)
> This seems to be some random issue as on same run all other tests pass:
> [12/91] (860s left) kms_frontbuffer_tracking
> (fbcpsr-2p-scndscrn-spr-indfb-fullscreen)
> Starting subtest: fbcpsr-2p-scndscrn-spr-indfb-fullscreen
> Subtest fbcpsr-2p-scndscrn-spr-indfb-fullscreen: SUCCESS (4.095s)
> [26/91] (818s left) kms_frontbuffer_tracking
> (psr-2p-scndscrn-cur-indfb-draw-pwrite)
> Starting subtest: psr-2p-scndscrn-cur-indfb-draw-pwrite
> Subtest psr-2p-scndscrn-cur-indfb-draw-pwrite: SUCCESS (4.584s)
> [27/91] (813s left) kms_frontbuffer_tracking
> (psr-2p-scndscrn-spr-indfb-onoff)
> Starting subtest: psr-2p-scndscrn-spr-indfb-onoff
> Subtest psr-2p-scndscrn-spr-indfb-onoff: SUCCESS (5.191s)
> [38/91] (552s left) kms_frontbuffer_tracking
> (fbcpsr-2p-primscrn-spr-indfb-onoff)
> Starting subtest: fbcpsr-2p-primscrn-spr-indfb-onoff
> Subtest fbcpsr-2p-primscrn-spr-indfb-onoff: SUCCESS (5.991s)
> [69/91] (109s left) kms_frontbuffer_tracking
> (fbc-2p-scndscrn-pri-shrfb-draw-mmap-cpu)
> Starting subtest: fbc-2p-scndscrn-pri-shrfb-draw-mmap-cpu
> Subtest fbc-2p-scndscrn-pri-shrfb-draw-mmap-cpu: SUCCESS (2.707s)
> 
> Starting subtest: pipe-A-cursor-128x128-onscreen
> Subtest pipe-A-cursor-128x128-onscreen: SUCCESS (6.783s)
> [86/91] ( 29s left) kms_frontbuffer_tracking
> (fbc-2p-scndscrn-cur-indfb-draw-blt)
> Starting subtest: fbc-2p-scndscrn-cur-indfb-draw-blt
> Subtest fbc-2p-scndscrn-cur-indfb-draw-blt: SKIP (0.000s)
> 
> I would call this invalid bug?

Sorry, but the bug is very valid. It happened 3 times in the same shard...

As you said IRL, some of the *2p* tests are passing on the same shard, which
might exclude HW change (unless someone rebooted the chamelium while running
the shard).

So, we now need to investigate in the kernel logs what might have happened.
Disappearing outputs is cause for concern.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190620/b6106849/attachment.html>