Created attachment 84085 [details]
dmesg

System Environment:
--------------------------
Platform:    Pineview/Ironlake/Sandybridge/Ivybridge/Haswell
Kernel:     (drm-intel-fixes)3d51af04567800a87a04785d375f1258977ef6d7

Bug detailed description:
-----------------------------
It skip on Pineview/Ironlake/Sandybridge/Ivybridge/Haswell with -fixes kernel.
It works well on -queued and -nightly kernel.
igt/gem_pread_after_blit/normal-display also skipped.

Bisect shows:7553ad6e10f76aa703359a10e08138e14501d54d is the first bad commit
commit 7553ad6e10f76aa703359a10e08138e14501d54d
Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Mon Aug 12 10:43:59 2013 +0200
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Mon Aug 12 11:17:58 2013 +0200

    tests: use drmtest_skip() in caching ioctl helpers

    This way we can rip out all the skip handling from the test control flow,
    and additionally (by using drmtest_retval()) even get correct exit codes.

    The only tricky part is that when we only want ot skip parts of a test
    (like for gem_pread and gem_pwrite) we need to split out those parts as
    subtests. But no addition of control-flow is required, the set/longjmp
    magic in the helpers all makes it happen.

    Also we make extensive use of the behaviour of drmtest_skip to skip
    all subsequent subtests if it is called outside of a subtest. This allows
    us to re-flatten the control flow a lot.

    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>


Test requirement not met in function gem_set_caching, file drmtest.c:421:
Test requirement: (ret == 0)
Subtest interruptible-display: SKIP


Reproduce steps:
----------------------------
1. ./gem_pread_after_blit --run-subtest interruptible-display