[Bug 72102] New: [BDW]igt/gem_reloc_vs_gpu/forked-faulting-reloc-thrash-inactive causes assertion failure function

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 72102
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [BDW]igt/gem_reloc_vs_gpu/forked-faulting-reloc-thrash
                    -inactive causes assertion failure function
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: jinxianx.guo at intel.com
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Intel
           Product: DRI

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

System Environment:
--------------------------
Platform: Broadwell
kernel   (drm-intel-nexe-queued)8b4f49e03901e82898540bd1189333edf9588d74
Some additional commit info:
Author: Jesse Barnes <jbarnes at virtuousgeek.org>
Date:   Mon Nov 25 15:51:16 2013 -0800

    drm/i915: split fb allocation and initialization v2

    If we use a stolen buffer, our probe callback shouldn't allocate a new
    buffer; we should re-use the one from the BIOS instead if possible.

    v2: fix locking (Jesse)

Bug detailed description:
-----------------------------
Assertion failure shown while run the case.

This is the first time to run igt test on Broadwell.

Following cases also have this issue.
igt/gem_reloc_vs_gpu/forked-faulting-reloc-thrashing
igt/gem_reloc_vs_gpu/forked-interruptible-faulting-reloc-thrash-inactive
igt/gem_reloc_vs_gpu/forked-interruptible-faulting-reloc-thrashing
igt/gem_reloc_vs_gpu/forked-interruptible-thrash-inactive
igt/gem_reloc_vs_gpu/forked-interruptible-thrashing
igt/gem_reloc_vs_gpu/forked-thrash-inactive
igt/gem_reloc_vs_gpu/forked-thrashing

Error log:
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
child 0 failed with exit status 99
Subtest forked-faulting-reloc-thrash-inactive: FAIL
gem_reloc_vs_gpu: drmtest.c:1181: children_exit_handler: Assertion
`kill(test_children[nc], 3) == 0' failed.
Test assertion failure function gem_execbuf, file drmtest.c:556:
Test assertion failure function gem_execbuf, file drmtest.c:556:
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Failed assertion: ret == 0
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Aborted (core dumped)

Steps:
---------------------------
./gem_reloc_vs_gpu --run-subtest forked-faulting-reloc-thrash-inactive

-- 
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/20131128/8eedf399/attachment-0001.html>