[Bug 60002] [PNV]I-G-T/=?UTF-8?Q?kms=5Fflip=20subtest=EF=BC=9A?='blocking-absolute-wf_vblank' fail

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from shui yangwei <yangweix.shui at intel.com> ---
(In reply to comment #1)
> Created attachment 78651 [details] [review]
> fix for initial console blank state
> 
> So, after some discussions on IRC with one part of the solution is to force
> a full modeset to make sure we unblank if we started the test with a blanked
> state.
> 
> A patch for this is attached could you try it on your box with the command
> sequence I posted in my previous comment?
> 
> A secondary issue that can happen is blanking _during_ the test, for that we
> need to prevent blanking from within the test app, we'll follow-up with a
> patch for that too.

I tried the patch you appended on -nightly top, the result is just like yanbing
reported: "The first time is pass,but after that always fail". I list the
phenomenon below, if anything you needed I haven't described clearly, please
comment.
-------------------------------------------------------------
[root at x-pnv1 tests]# ./kms_flip --run-subtest blocking-absolute-wf_vblank
Using monotonic timestamps
running testcase: blocking-absolute-wf_vblank
could not find requested crtc 3
Beginning blocking-absolute-wf_vblank on crtc 4, connector 5
  1024x600 60 1024 1048 1184 1438 600 603 604 628 0xa 0x48 54200
.............................................................
blocking-absolute-wf_vblank on crtc 4, connector 5: PASSED

[root at x-pnv1 tests]# echo $?
0
[root at x-pnv1 tests]# ./kms_flip --run-subtest blocking-absolute-wf_vblank
Using monotonic timestamps
running testcase: blocking-absolute-wf_vblank
could not find requested crtc 3
Beginning blocking-absolute-wf_vblank on crtc 4, connector 5
  1024x600 60 1024 1048 1184 1438 600 603 604 628 0xa 0x48 54200
.run_test_step:732 failed, ret=-16, errno=16
Aborted (core dumped)
[root at x-pnv1 tests]# echo $?
134

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130502/b3023e0f/attachment.html>