[Bug 84859] New: [BYT]igt/gem_persistent_relocs/forked-interruptible-faulting-reloc-thrashing fails

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Oct 9 23:23:46 PDT 2014


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

            Bug ID: 84859
           Summary: [BYT]igt/gem_persistent_relocs/forked-interruptible-fa
                    ulting-reloc-thrashing fails
           Product: DRI
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: huax.lu at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 107648
  --> https://bugs.freedesktop.org/attachment.cgi?id=107648&action=edit
dmesg

==System Environment==
--------------------------
Regression: not sure, only reproduce on -nightly kernel.

==kernel==
--------------------------
drm-intel-nightly/ea4bec8e96ea8b33b49a7892c1c7f20041a56da6

==Bug detailed description==
It fails on BYT with drm-intel-nightly kernel. it pass on drm-intel-queued,
drm-intel-fixes, drm-fixes and drm-next kernel.

igt/gem_persistent_relocs/forked-interruptible-thrashing and
igt/gem_reloc_vs_gpu/forked-interruptible-faulting-reloc-thrashing also fail.

output:
IGT-Version: 1.8-g7f82289 (x86_64) (Linux:
3.17.0_drm-intel-nightly_ea4bec_20141009+ x86_64)
Test assertion failure function do_test, file gem_persistent_relocs.c:260:
Failed assertion: test == 0xdeadbeef
Last errno: 4, Interrupted system call
mismatch in buffer 0: 0x00000000 instead of 0xdeadbeef at offset 256
child 3 failed with exit status 99
Subtest forked-interruptible-faulting-reloc-thrashing: FAIL (451.180s)

==Reproduce steps==
---------------------------- 
1. ./gem_persistent_relocs --run-subtest
forked-interruptible-faulting-reloc-thrashing

-- 
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: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141010/9bd483a8/attachment.html>


More information about the intel-gfx-bugs mailing list